[PR #5067] [CLOSED] docs(gemini): diagnose model schema rejection separately from MCP setup #6766

New issue

Closed

opened 2026-11-01 21:42:54 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:42:54 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5067
Author: @ashukumar-tech
Created: 10/18/2026
Status: ❌ Closed

Base: main ← Head: docs/gemini-invalid-argument-diagnostics

📝 Commits (2)

95339e3 docs(gemini): distinguish MCP setup from model schema rejection
a08bf33 docs(gemini): use registered gemini_cli client ID

📊 Changes

1 file changed (+35 additions, -0 deletions)

View changed files

📝 docs/client-configuration.md (+35 -0)

📄 Description

Summary

Refs #4620 and #3246.

Users who see Gemini CLI 400 INVALID_ARGUMENT may mistake a model-side tool-schema rejection for a Ghidra failure or assume, without a captured rejected request, that the full MCP catalog size is the proven cause. This adds a short, actionable diagnostic path to the existing Gemini CLI client guide.

Change

Distinguish REA MCP configuration/doctor health from the downstream model API accepting advertised tool schemas.
Provide an A/B test with the REA registration enabled and disabled.
Document the existing REA_MCP_INPUT_SCHEMA_PROFILE=compact option as a diagnostic, explicitly stating that it does not narrow the tool count and cannot guarantee API acceptance.
Ask for sanitized, stage-specific evidence and link the existing tool-family scoping proposal (#3246).

No runtime, tool registration, analysis, or security behavior changes.

Verification and limits

Source-reviewed existing docs/client-configuration.md, src/config/mcpInputSchemaProfile.ts and related client-profile documentation.
GitHub compare verified exactly one Markdown file changed: 35 additions, no deletions.
Not run: documentation site build, live Gemini CLI, provider API request, or other tests. The reported 400 is not independently reproduced. This PR does not claim to fix it.
Request maintainer feedback on whether this guidance belongs in client configuration or a separate troubleshooting reference.

Author readiness

Human owner: @ashuk422993-dotcom

I reviewed the complete diff and take responsibility for this AI-assisted contribution.
I checked the supporting evidence and documented any verification gaps.
I declare this PR ready for initial maintainer review.

Ready for maintainer review. The verification gaps listed above remain open.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5067 **Author:** [@ashukumar-tech](https://github.com/ashukumar-tech) **Created:** 10/18/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/gemini-invalid-argument-diagnostics` --- ### 📝 Commits (2) - [`95339e3`](https://github.com/morluto/rea/commit/95339e39e718a5f8c7e5e17e18e60337c7a365fb) docs(gemini): distinguish MCP setup from model schema rejection - [`a08bf33`](https://github.com/morluto/rea/commit/a08bf33ba17ac298dc97779d52368ee1bd2923a0) docs(gemini): use registered gemini_cli client ID ### 📊 Changes **1 file changed** (+35 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+35 -0) </details> ### 📄 Description ## Summary Refs #4620 and #3246. Users who see Gemini CLI `400 INVALID_ARGUMENT` may mistake a model-side tool-schema rejection for a Ghidra failure or assume, without a captured rejected request, that the full MCP catalog size is the proven cause. This adds a short, actionable diagnostic path to the existing Gemini CLI client guide. ## Change - Distinguish REA MCP configuration/doctor health from the downstream model API accepting advertised tool schemas. - Provide an A/B test with the REA registration enabled and disabled. - Document the existing `REA_MCP_INPUT_SCHEMA_PROFILE=compact` option as a **diagnostic**, explicitly stating that it does not narrow the tool count and cannot guarantee API acceptance. - Ask for sanitized, stage-specific evidence and link the existing tool-family scoping proposal (#3246). No runtime, tool registration, analysis, or security behavior changes. ## Verification and limits - Source-reviewed existing `docs/client-configuration.md`, `src/config/mcpInputSchemaProfile.ts` and related client-profile documentation. - GitHub compare verified exactly one Markdown file changed: 35 additions, no deletions. - **Not run:** documentation site build, live Gemini CLI, provider API request, or other tests. The reported 400 is not independently reproduced. This PR does not claim to fix it. - Request maintainer feedback on whether this guidance belongs in client configuration or a separate troubleshooting reference. ## Author readiness Human owner: @ashuk422993-dotcom - [x] I reviewed the complete diff and take responsibility for this AI-assisted contribution. - [x] I checked the supporting evidence and documented any verification gaps. - [x] I declare this PR ready for initial maintainer review. Ready for maintainer review. The verification gaps listed above remain open. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-11-01 21:42:54 +00:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#6766

No description provided.

Rows
Columns