You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: outputSchema for mcp tools should be exposed to LLM #27577
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
For MCP tools, the optional outputSchema provides information about the output to expect from the tool. But opencode is not including this in context, only the tool description. According to the MCP spec:
Providing an output schema helps clients and LLMs understand and properly handle structured tool outputs by:
...
Guiding clients and LLMs to properly parse and utilize the returned data
so I think the information from tool's outputSchema should be included in the LLM context in some way.
changed the title [-][FEATURE]: output_schema (in some format) for mcp tools should be exposed to LLM[/-][+][FEATURE]: outputSchema for mcp tools should be exposed to LLM[/+]on May 14, 2026
previously I'd checked making manual curl requests to my MCP server that it was returning the outputSchema with descriptions, and asked the LLM in opencode for full description it had of the MCP tool, and if it sees "string from description of output parameter" anywhere in it's context, and it said it didn't see the string, and the description it returned was the tool description without anything about the outputSchema. then I searched issues for outputSchema and found #21591 where someone (well with emdash so probably an llm) says "opencode doesn't use outputSchema — it only reads inputSchema in convertMcpTool()".
and just now to be completely sure I ran opencode through mitmproxy, and for the MCP tool it is sending:
Activity
[-][FEATURE]: output_schema (in some format) for mcp tools should be exposed to LLM[/-][+][FEATURE]: outputSchema for mcp tools should be exposed to LLM[/+]rekram1-node commentedon May 14, 2026
wdym, im pretty sure we respect this can u show me how we arent?
bo-tato commentedon May 14, 2026
previously I'd checked making manual curl requests to my MCP server that it was returning the outputSchema with descriptions, and asked the LLM in opencode for full description it had of the MCP tool, and if it sees "string from description of output parameter" anywhere in it's context, and it said it didn't see the string, and the description it returned was the tool description without anything about the outputSchema. then I searched issues for outputSchema and found #21591 where someone (well with emdash so probably an llm) says "opencode doesn't use outputSchema — it only reads inputSchema in convertMcpTool()".
and just now to be completely sure I ran opencode through mitmproxy, and for the MCP tool it is sending:
but the outputSchema is not present, and searching the strings from the descriptions in the outputSchema with mitmproxy they are not being sent at all
rekram1-node commentedon May 15, 2026
oh ic what ur saying now i was misunderstanding
github-actions commentedon Jul 14, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.