[tools] add support for structured responses #81
Conversation
|
Nice job! Does this not also require an 'outputSchema'? |
|
output schema is optional for structured output, for now I just added support for the response field |
test/test_helper.rb
Outdated
| @@ -17,7 +17,7 @@ | |||
|
|
|||
| require_relative "instrumentation_test_helper" | |||
|
|
|||
| Minitest::Reporters.use!(Minitest::Reporters::ProgressReporter.new) | |||
| Minitest::Reporters.use!(Minitest::Reporters::ProgressReporter.new) unless ENV["RM_INFO"] | |||
There was a problem hiding this comment.
Can you explain where/when RM_INFO comes from? (Explicitly calling out this change in the PR description or punting it to its specific PR would be favourable.)
There was a problem hiding this comment.
created a new PR here https://github.com/modelcontextprotocol/ruby-sdk/pull/97/files
| attr_reader :content, :is_error | ||
|
|
||
| # @param structured_content [Hash] The structured content of the response, must be provided. | ||
| # @param content [String, nil] The content array of the response, can be nil. If nil will generate a single element with structured content converted to JSON string. |
There was a problem hiding this comment.
For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block.
Not a MUST, but a SHOULD, but I agree with doing it for backwards compatibility in this gem.
- add support for structured content (https://modelcontextprotocol.io/specification/2025-06-18/server/tools#structured-content) in tool responses - for backwards compatibility implements text content auto-generation
honzasterba
force-pushed
the
structured_response_support
branch
from
71346ef to
3431c23
Compare
|
separated unrelated change into new PR |
Add new response class to be able to return structuredContent as part of tools response in a backwards compatible way
Motivation and Context
Structured responses are an established part of the spec and the SDK should support it.
How Has This Been Tested?
Add new tested and tested with internal MCP server implementation.
Breaking Changes
None
Types of changes
Checklist