Content
View differences
Updated by Jan Sandbrink 5 days ago
**As** a user of an LLM interacting with OpenProject
**I want to** remove the HTML portion of formattables from MCP responses,
**so that** costs for running language models are kept lower and smaller language models can still use the results.
**Acceptance criteria**
* The `html` of formattable properties is stripped from results
* Only one representation of the description is preserved and directly mapped to the attribute "description"
* Needs discussion which one
* The corresponding MCP output schema is adapted accordingly (without making the API schema worse)
* aim for a simple solution that generates a valid schema, e.g. removing `required` from every MCP output schema
* we might drop output schemas completely at a later point, see ##AI-67
**Technical context**
A quick analysis on 500 work packages from Community showed that the HTML description of work packages makes up about 20% of the total result size for a work package collection (in Bytes).
**I want to** remove the HTML portion of formattables from MCP responses,
**so that** costs for running language models are kept lower and smaller language models can still use the results.
**Acceptance criteria**
* The `html` of formattable properties is stripped from results
* Only one representation of the description is preserved and directly mapped to the attribute "description"
* Needs discussion which one
* The corresponding MCP output schema is adapted accordingly (without making the API schema worse)
* aim for a simple solution that generates a valid schema, e.g. removing `required` from every MCP output schema
* we might drop output schemas completely at a later point, see ##AI-67
**Technical context**
A quick analysis on 500 work packages from Community showed that the HTML description of work packages makes up about 20% of the total result size for a work package collection (in Bytes).