Skip to content

Conversation

@bigdevlarry
Copy link
Contributor

The changes add comprehensive support for outputSchema in the Tools definition, enabling MCP servers to specify the expected structure and types of tool responses.

This includes:

Added outputSchema parameter to Builder::addTool() method
Updated the Tool class constructor and JSON serialization to support outputSchema
Added validation for outputSchema structure and type requirements
Enhanced existing tests to verify outputSchema functionality works correctly
Fixed related type annotation issues and code style problems

Screenshot 2025-11-16 at 22 04 02 Screenshot 2025-11-16 at 22 04 14

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • [x ] I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@bigdevlarry
Copy link
Contributor Author

Hi @chr-hertel, & @CodeWithKyrian the OutputSchema support PR is back up

@bigdevlarry bigdevlarry force-pushed the add-support-for-output-schema branch from ec01d9a to a2d7b6d Compare November 16, 2025 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant