MCP Fix — tools/call Accepts null and Stringified Arguments
ChatGPT connectors and OpenAI function-calling bridges that send arguments as null or JSON strings no longer fail the MCP request schema on Aveiro's hosted server.
Some MCP clients send tools/call with arguments: null, an empty string, or a JSON string instead of an object. Aveiro's hosted MCP endpoint now normalizes those shapes before the SDK validates the request.
What we fixed
The MCP tools/call schema expects arguments to be an object or absent. Real clients do not always match that shape:
Stringified JSON — OpenAI native function-calling can emit arguments as a JSON string; some bridges forward that format unchanged
Empty string — treated like no arguments
Aveiro's hosted MCP endpoint at https://www.aveiro.app/api/mcp/mcp now normalizes these variants before the SDK parses the JSON-RPC message:
Client sends
Aveiro accepts
`arguments: null`
Field omitted (same as no arguments)
`arguments: ""`
Field omitted
`arguments: "{"site_id":"…"}"`
Parsed to a plain object
`arguments: { … }`
Unchanged
Unparseable strings are left as-is so the SDK can return a normal validation error.This complements the parameterless tools fix — together, more MCP clients can call Aveiro tools without InvalidParams on argument shape alone.
Who benefits
ChatGPT and other connectors that send null for optional argument fields
OpenAI function-calling integrations that stringify tool arguments
Any MCP client bridging from a host that does not emit strict JSON objects
No token, scope, or reconnect changes are required. Retry the tool call if a session cached an older error.