Is your feature request related to a problem? Please describe.
Previously, the functionality worked for @get methods but not for other HTTP methods. I’ve updated mcp-inspector to support those as well.
However, there’s an issue with how the MCP SDK handles object parameters. When a tool is invoked with object inputs, the SDK automatically wraps them in an extra nested structure.
MCP SDK automatically wraps object parameters, creating:
{"currency": {"currency": {...actual data...}}} // Double-wrapped
Instead of:
{"currency": {...actual data...}} // Expected
Notice the double-wrapping: currency → currency again inside.
Describe the solution you'd like
Handle this at the factory handler entry point by unwrapping the extra nesting layer, ensuring the parameters match the expected structure before further processing.
Describe alternatives you've considered
I attempted to adjust the schema directly to account for this behavior, but that approach doesn’t address the root cause and isn’t a reliable fix.
Is your feature request related to a problem? Please describe.
Previously, the functionality worked for @get methods but not for other HTTP methods. I’ve updated mcp-inspector to support those as well.
However, there’s an issue with how the MCP SDK handles object parameters. When a tool is invoked with object inputs, the SDK automatically wraps them in an extra nested structure.
MCP SDK automatically wraps object parameters, creating:
{"currency": {"currency": {...actual data...}}} // Double-wrapped
Instead of:
{"currency": {...actual data...}} // Expected
Notice the double-wrapping: currency → currency again inside.
Describe the solution you'd like
Handle this at the factory handler entry point by unwrapping the extra nesting layer, ensuring the parameters match the expected structure before further processing.
Describe alternatives you've considered
I attempted to adjust the schema directly to account for this behavior, but that approach doesn’t address the root cause and isn’t a reliable fix.