FAQ · P1

MCP tool schema size vs strict clients

When connecting REA makes the entire agent refuse every request.

What breaks

Some providers enforce a per-tool JSON schema size cap. REA’s full tools/list can advertise many detailed tools; a single oversized schema may cause Moonshot/Kimi-class clients to reject the whole session.

What to do (operator)

Upgrade rea-agents — schema compaction and discovery fixes ship over time.
Prefer clients that tolerate large catalogs, or use CLI for heavy jobs.
Watch upstream roadmap work on bounded-resource MCP usability; do not “fix” caps by corrupting schemas.

Related: domain-split proxy

When you need a smaller catalog without amputating capability, a community stdio filter proxy can expose only selected domain groups. See MCP domain-split proxy and the companion showcase dsh-mcp-rea (curated face + CLI escape hatch).

This is a compatibility problem, not permission to bypass vendor limits with malformed tool descriptors.