fix(server): trim tool and parameter descriptions under client context caps by SavioBS629 · Pull Request #486 · browserstack/mcp-server · GitHub
Skip to content

fix(server): trim tool and parameter descriptions under client context caps - #486

Open
SavioBS629 wants to merge 2 commits into
mainfrom
feat/trim-tool-descriptions
Open

SavioBS629 wants to merge 2 commits into
mainfrom
feat/trim-tool-descriptions

Conversation

@SavioBS629

Copy link
Copy Markdown
Collaborator

No description provided.

…t caps

Every client loads all tool descriptions at connect time. Kiro's power
activation renders them into one tool result capped at 30,000 chars; ours
was ~41,000, so Kiro truncated it to a 500-char preview and the agent
guessed tool names that do not exist.

Rewrites descriptions toward the documented budget (tool <=200 chars,
param <=120): shared precondition constants, standalone description
constants, and the capability-registry tools. Every routing rule is kept
(listProducts first, ask on a clash, describe before invoke, weak_match
re-search, '*' browse, paging, user_permission for writes, deletes
refused), and every phrase pinned by tests is unchanged.

Rendered size of the 44 hosted tools: 41,351 -> 27,512 chars.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

@SavioBS629
SavioBS629 marked this pull request as draft October 14, 2026 14:08
Shorten Percy setup/scan parameter text and the createTestCase /
updateTestCase parameter text without changing their meaning.
Saves ~500 tokens on the 52-tool list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@sarve-shreyas
sarve-shreyas marked this pull request as ready for review October 21, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants