chore(mcp): remove researchMode from query-docs tool params#2524
Merged
Conversation
Hide the `researchMode` parameter from the MCP tool's input schema so agents stop invoking it. The upstream `/api/v2/context` route still accepts and serves the parameter; only the MCP-layer surface is removed. Reasoning: several MCP clients hit per-request timeouts (60s defaults in the SDK and in fetch-wrappers) on long-running research calls in ways that can't all be solved server-side. Until the timeout story is reliable across clients, agents shouldn't be able to call it via MCP. Updates: - Drop the `researchMode` field from the `query-docs` input schema. - Drop the workflow line in the tool description that referenced it. - Stop forwarding `researchMode` to fetchLibraryContext; the field is optional on ContextRequest, so omitting it is equivalent to false.
enesakar
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hide the
researchModeparameter from the MCP tool's input schema so agents stop invoking it. The upstream/api/v2/contextroute still accepts and serves the parameter; only the MCP-layer surface is removed. Reasoning: several MCP clients hit per-request timeouts (60s defaults in the SDK and in fetch-wrappers) on long-running research calls in ways that can't all be solved server-side. Until the timeout story is reliable across clients, agents shouldn't be able to call it via MCP.Updates:
researchModefield from thequery-docsinput schema.researchModeto fetchLibraryContext; the field is optional on ContextRequest, so omitting it is equivalent to false.