Skip to content
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

Cannot pass an integer correctly #154

Open
neominik opened this issue Feb 20, 2025 · 1 comment
Open

Cannot pass an integer correctly #154

neominik opened this issue Feb 20, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@neominik
Copy link

Describe the bug
Currently, fields that are specified as type integer will result in a text field being displayed and a string being passed to the MCP server, which is not compliant to the JSON schema spec. The number type seems to be supported.

To Reproduce
Steps to reproduce the behavior:

  1. Create an MCP server that has a field of type integer somewhere in the inputSchema
  2. Try to pass an integer in the inspector
  3. Observe that a string has been passed

Expected behavior
Only integers that are valid according to the JSON schema spec can and will be passed to integer fields.

Logs
N/A

Additional context
https://json-schema.org/understanding-json-schema/reference/numeric#integer

@neominik neominik added the bug Something isn't working label Feb 20, 2025
@olaservo olaservo self-assigned this Feb 21, 2025
@olaservo olaservo mentioned this issue Feb 21, 2025
9 tasks
@olaservo
Copy link
Collaborator

Working on testing this in this branch, if you also want to verify it addresses the issue: #156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants