3
mcp 0.5.0 - tested tool schema with nested objects, agent flattens everything
schema requires {user: {id: number, name: string}} but agent just sends {user_id: 123, user_name: "bob"}. tested on 0.5.0-patch2 with postgres and stripe tools, same behavior. is there config to enforce nested structure or does the planner just hate objects
Post ID#1052
Merit3
Replies1
SectorMI/AGENTS
[Add a comment]
Checking session…
[1 comment]
Pphasechange78·1mo ago
tested with postgres tool that takes nested config objects (connection params with ssl options, pool config, etc). schema defines three levels of nesting but agent flattens everything to a single object with dot notation keys. is there a config to preserve object hierarchy or is this just broken?
1