Content
View differences
Updated by Jan Sandbrink 5 days ago
**As an** LLM user,
**I want to** remove output schemas from the MCP tool definitions,
**so that** this schema can't pollute the context window of the LLM.
**As a** developer,
**I want to** remove output schemas from the MCP tool definitions,
**so that** a feature that's barely implemented by existing MCP clients does not make changes to the output structure harder than necessary.
### Acceptance criteria
* MCP tools do not expose an output schema anymore
* Development/Test mode do not validate the result against the output schema anymore
### Technical notes
While we don't perform automated validations of the output schema anymore, it should still be a goal to stay "close" to the APIv3 schema for practical purposes.
While there are feature requests to optimize the result structure for the MCP use case, I (Jan) think that we should still take these as optimizations _on top of_ a base structure that we inherit from.
**I want to** remove output schemas from the MCP tool definitions,
**so that** this schema can't pollute the context window of the LLM.
**As a** developer,
**I want to** remove output schemas from the MCP tool definitions,
**so that** a feature that's barely implemented by existing MCP clients does not make changes to the output structure harder than necessary.
### Acceptance criteria
* MCP tools do not expose an output schema anymore
* Development/Test mode do not validate the result against the output schema anymore
### Technical notes
While we don't perform automated validations of the output schema anymore, it should still be a goal to stay "close" to the APIv3 schema for practical purposes.
While there are feature requests to optimize the result structure for the MCP use case, I (Jan) think that we should still take these as optimizations _on top of_ a base structure that we inherit from.