Skip to content

Make content canonical instead of structuredContent #131

Description

@Gabriel-Darbord

Problem

Currently, the MCP tools return both a summary in the content field, and the full response in the structuredContent field.
However, while the specification is not too clear, it is the content field that is the canonical response meant for the LLM, and structuredContent is meant for programmatic uses.

Some agents, such as OpenCode, only choose one of the two to send to the LLM, and when agents prefer content then LLMs get almost no useful information.
Other agents, such as Codex, send both, which can be considered a waste, especially since the content data is also part of structuredContent.

Solution

Make the MCP configurable: whether to send only content, only structuredContent, or both.
The content data should be enhanced to contain all of the relevant information, and it doesn't need to be structured: it can be any form of plain text, such as bullet points to represent lists.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions