Skip to content

McpServer builder extensions result in Tool InputSchema which isn't spec compliant #342

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.

Sign up for GitHub

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

Jump to bottom
Open
PederHP opened this issue Apr 22, 2025 · 0 comments · May be fixed by #343
Open

McpServer builder extensions result in Tool InputSchema which isn't spec compliant #342

PederHP opened this issue Apr 22, 2025 · 0 comments · May be fixed by #343
Assignees
@PederHP
Labels
bug Something isn't working

Comments

@PederHP
Copy link
Collaborator

PederHP commented Apr 22, 2025 •
edited
Loading

When using the JsonSchema from AIFunction additional properties not support by MCP are present. This can break clients which expect the Tool objects to follow the spec schema fully (InputSchema does not support additional properties).

GitHub Copilot (at least some versions of it) is an example of a client which will not accept the additional properties (e.g. "title", "description"). So even a minimalist MCP Server created using the README example or SDK samples will fail with such clients.

I'll have a PR with a fix soon. Just creating this for tracking purposes.
@PederHP PederHP added the bug Something isn't working label Apr 22, 2025
@PederHP PederHP self-assigned this Apr 22, 2025
@PederHP PederHP linked a pull request Apr 22, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PederHP PederHP

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Validate and filter inputSchema for McpServerTool so it is spec compliant PederHP/csharp-sdk
1 participant
@PederHP