Open
Conversation
d43af83 to
a21edfa
Compare
a21edfa to
2361d48
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

TL;DR
Added structured output support to the agent server through a new MCP server that provides a
submit_resulttool for agents to return JSON Schema-validated results. This is used by workflows agents that need to return a structured output defined by the user.What changed?
ResultMcpServerclass that runs an HTTP MCP server exposing asubmit_resulttool--outputSchemaCLI option to accept JSON Schema for structured output validationHow to test?
--outputSchema '{"type": "object", "properties": {"answer": {"type": "string"}}}'submit_resulttool to return data conforming to the schemaWhy make this change?
This enables agents to return structured, validated results instead of only creating PRs or branches.