MCP Fix — Parameterless Tools Work Without an Arguments Field
ChatGPT and other MCP clients that omit arguments on no-parameter tools no longer get InvalidParams on aveiro_me, aveiro_list_sites, or aveiro_social_list_accounts.
Some MCP clients skip the arguments field entirely when a tool has no parameters. Aveiro's hosted and stdio MCP servers now accept those calls instead of returning InvalidParams.
What we fixed
The Aveiro MCP server registers several parameterless tools — actions that need no input beyond your token:
aveiro_me — verify token, scopes, and allowed sites
aveiro_list_sites — list sites the token can access
aveiro_social_list_accounts — list connected Instagram/Threads accounts (social:write)
Some clients, including ChatGPT, send tool calls without an arguments field when a tool has no parameters. Our server previously registered an empty input schema for these tools, which made the MCP SDK reject those calls with InvalidParams.We removed the empty schema so the SDK advertises a compatible empty-object shape and invokes the handler correctly — whether the client sends {} or omits arguments entirely.
Who benefits
ChatGPT and other clients that omit arguments on zero-parameter tools
Cursor and Claude users calling aveiro_me during setup or health checks
Social agents listing accounts with aveiro_social_list_accounts before drafting posts
No token or scope changes are required. Reconnect or retry the tool call if you hit InvalidParams on an older session.