**As** a user of LLM tools
**I want to** have my MCP client resolve custom fields properly,
**so that** I can also work with properly named custom fields in my LLM interactions.

**Acceptance criteria**

* Begin of the insertionMCP server is extended in a way that clients can understand the meaning of custom fieldsEnd of the insertion Begin of the deletion <br>End of the deletion


**Technical notes**

* Begin of the insertionMost likely we will want to expose work package schemas as another tool/resourceEnd of the insertion Begin of the deletion <br>


**Permissions and visibility considerations**

* _To whom is this feature visible?_End of the deletion

* Begin of the insertionclients also need a wayEnd of the insertion Begin of the deletion _When is it not visible?_


**Translation considerations**

* _Key terms and phrases in the key languages_&nbsp;


**Out of scope**

* <br>


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the insertionfigure out which schemaEnd of the insertion Begin of the deletion include all teams necessaryEnd of the deletion to Begin of the insertionfetch for a given work packageEnd of the insertion Begin of the deletion be informed of the changes._End of the deletion