The cancel-reservation MCP tool has a broken schema

We isolated the issue to the Hospitable MCP server. When the hospitable MCP connection was removed from OpenClaw, the random schema errors stopped immediately, while Discord and WhatsApp continued working. The failing tools included hospitable__cancel-reservation and hospitable__get-community-user. This strongly suggests the remote MCP server is exposing one or more tool input schemas in a format OpenAI/GPT-5.4 rejects — most likely type: object schemas missing a properties field, and possibly other strict-schema requirements. Please review the MCP tool definitions for OpenAI compatibility.

Thanks for reporting, ​@LeviRenza . We’re on it. The challenge at the moment is solving tool + context bloat. We’re going to be at 40+ tools soon, and many more after that, some of them already having heavy schemas. This has lead to some agents starting to fail early. We’re experimenting with different ways of exposing lightweight schemas that agents can autonomously expand.

In our internal testing, agents typically *can* interpret the latest schema that we proposed, but it seems to depend on the client harness.