Replies: 2 comments 2 replies
-
This actually seems wider: any top-level allOf or anyOf with an object seems to have a problem. Here's an MRE: https://github.com/domdomegg/mcp-90-mre/blob/master/src/index.ts And a video of Claude struggling with it: Screen.Recording.2024-12-13.mp4 |
Beta Was this translation helpful? Give feedback.
1 reply
-
I think this is unrelated to MCP, but thank you for the detailed description of the issue and examples. Will pass it along to other teams at Anthropic. Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Discussion Topic
tldr: In the Claude desktop app, when using tools with parameter schemas that include allOf combined with object types, the parameter is converted to a string instead of being passed as an object, even when properly formatted in the XML tags.
Description
When using tools with parameter schemas that include
allOf
combined with object types, the parameter is being converted to a string instead of being passed as an object, even when properly formatted in the XML tags.Schema Example
The problematic tool input schema pattern looks like:
Reproduction Steps
allOf
schema containing object types (e.g. create_field)Error Message
Expected Behavior
Parameters matching an
allOf
schema with object types should be passed as objects, not converted to strings.System Information
Additional Notes
This appears specific to how the Anthropic app wrapper handles parameters when the schema uses
allOf
with object types. The parameter value is being stringified somewhere in the processing pipeline before reaching the tool.Beta Was this translation helpful? Give feedback.
All reactions