Skip to content

OutputSchema support to MCP tools #654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

bzsurbhi
Copy link

@bzsurbhi bzsurbhi commented May 7, 2025

Add outputSchema support to MCP tools

Motivation and Context

Implemented changes in PR for outputSchema

Key implementation details:

  1. Added outputSchema field to the Tool class to store the JSON schema for tool outputs
  2. Enhanced func_metadata to extract return type annotations and generate JSON schemas
  3. Graceful error handling when schema generation fails (logs warning but doesn't break functionality)

How Has This Been Tested?

Added tests with tools using various return types including:

  • Simple types (string, int, bool)
  • Complex types (Pydantic models)
  • None return types
  • Collection types (lists, dictionaries)

Breaking Changes

No breaking changes. The outputSchema is optional and backward compatible with existing tools.

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
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@bzsurbhi bzsurbhi marked this pull request as draft May 13, 2025 22:16
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