Allow output schema to be array of objects #144
Merged
+72
−38
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.
This change allows you to declare the output schema as an array of objects.
When building an MCP, you might want to return a list of results while still providing a schema for those results. This helps clients better understand the data being returned.
Motivation and Context
One of the MCPs I'm building need to respond with list of items. And I'd like to provide a schema for this. Currently this is not possible (#142).
How Has This Been Tested?
I tried to test in
@modelcontextprotocol/inspector
but Inspector doesn't support it yet (modelcontextprotocol/inspector#552)In real application it seems to work fine.
Breaking Changes
OutputSchema class no longer expose
#properties
,#required
. But most likely they were not used by any consumer. Other than this, no breaking changes and user do not need to update existing configurations.Types of changes
Checklist
Additional context