WebFV
REA / Field guide

Separate REA schema errors from setup failures

Version mismatch, schema size, and gateway rejection need different fixes.

By WebFV Editorial · Checked October 21, 2026 · REA 6.7.0 · source issue 5160

What the evidence coversREA 6.7.0 full and compact MCP tool catalogs tested locally. Gateway outcomes are attributed to the upstream issue; no paid model request is claimed.

A schema rejection is not an engine diagnosis

If your client starts REA but a model provider rejects a tool definition, inspect the schema error before reinstalling Ghidra or changing binary paths. MCP transport, tool schema acceptance and analysis engines are separate layers. A fix for one does not establish the others.

This guide separates three failure classes discussed in REA issue 5160: older reference/recursion problems, schema size rejection, and client-provider compatibility. The issue's gateway results are reports from the participants, not WebFV's reproduction of a paid model request.

1. Establish the version actually running

Read the client's server registration. If it launches npx -y rea-agents@6.3.0 mcp, checking a global CLI at 6.7.0 does not prove the client uses 6.7.0. Likewise, editing a configuration does not guarantee that a still-running server process has restarted.

Record the configured command and package version. Stop and restart the integration through the client after updating. Confirm the process or client log identifies the intended version, where that information is available. Avoid clearing every package cache as a first move: it can remove useful evidence without addressing a version pinned in configuration.

Our setup guide uses an explicit 6.7.0 registration so the requested version is visible. The configuration checker can check field structure, but it cannot tell which cached or running package a client has loaded.

2. Match the error category

Error category What to inspect What not to infer
Reference, recursion, or object/string schema mismatch Active REA version; the exact rejected tool definition That all current releases have the same old defect
Schema exceeds maximum allowed size Size of the expanded tool schema; provider limits; available compact mode That the JSON configuration is invalid
Client-specific validation rejection Client version, gateway, model and schema dialect That another client/provider combination will behave identically
Command cannot start or transport disconnects Runtime, command arguments, permissions and client logs That a model schema limit was reached

Keep the first error message and tool name. A later generic “tool unavailable” message can hide the initial reason the client rejected the tool list.

3. Use issue 5160 as a versioned lead

The issue discusses an older cached 6.3.0 package and later testing around 6.7.0. It reports different outcomes for different tool schemas: a change that helped one tool did not establish that a larger schema was accepted by the same gateway. In that report, compact mode helped with a remaining size problem.

This is a diagnostic lead, not a universal repair command. Read the current issue and the release notes before changing production configuration. Record the mode you used so a later successful test is not incorrectly attributed only to a package update.

For REA 6.7.0, the documented switch is the environment variable REA_MCP_INPUT_SCHEMA_PROFILE=compact. Set it on the REA server registration, then fully reconnect or restart that server. It is an environment setting, not a guessed CLI argument.

For a JSON client such as Claude Code, the registration is:

{
  "mcpServers": {
    "rea": {
      "command": "npx",
      "args": ["-y", "rea-agents@6.7.0", "mcp"],
      "env": {"REA_MCP_INPUT_SCHEMA_PROFILE": "compact"}
    }
  }
}

For Codex TOML, keep the existing command and arguments and add the same setting in the REA server's environment table:

[mcp_servers.rea.env]
REA_MCP_INPUT_SCHEMA_PROFILE = "compact"

Use the actual server name if it differs from rea, and merge into an existing environment table instead of defining it twice. Back up the configuration before editing. The JSON checker on this site does not validate TOML.

What changed in our local catalog test?

We initialized the official 6.7.0 MCP server twice with a small stdio test client: once with the default profile and once with the compact environment setting. Both returned 207 tool definitions. The table counts JavaScript JSON.stringify(inputSchema).length code units, not UTF-8 bytes or provider tokens.

Tool Default profile Compact profile
capture_native_ui_scenario 2,090 1,527
compare_web_captures 165,694 891

This verifies that the setting changes the advertised schema projection in this release. It does not prove a particular gateway will accept it, that a model can invoke every tool correctly, or that the complete catalog fits a provider's limit. Recheck the actual failing request after restarting your client. If it still fails, retain the exact tool name and error category.

4. Reduce the reproduction safely

Use a temporary client profile and an empty working directory. Pin the package version. Start with the smallest relevant tool set or documented compact mode. Keep the same client and gateway while changing one variable at a time. This makes a result attributable to the version or mode you actually changed.

A meaningful comparison records: package version, active process version when visible, client/version, model gateway, tool name, mode, error class and outcome. “Works now” without those fields is hard to reproduce and can conceal an unrelated model or client switch.

Never post authentication headers or full environment maps with the report. If a schema includes sensitive descriptions or generated project data, reduce it to a safe example before sharing. The local checker report intentionally omits configuration values, but a client's debug log may not.

When to return to setup

If REA never starts, use REA setup and doctor interpretation first. If the connection succeeds and the provider rejects a schema, keep investigating the schema layer. If a tool is accepted but analysis fails, move to the selected engine's readiness and tool-specific error.

Sources: upstream issue 5160, 6.7.0 release notes, and installation documentation. No claim is made that every reported issue is still open or affects every current client.