[Jihaochang1]

Summary

• prefix maxToolInputElements refusals with Input validation error:
• consistent with existing pattern at line 374 for parseResult errors

Related to #3113 (already resolved by another contributor)

[changeset-bot]

🦋 Changeset detected

Latest commit: cf55a34

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@modelcontextprotocol/server	Patch
@modelcontextprotocol/client	Patch
@modelcontextprotocol/codemod	Patch
@modelcontextprotocol/core	Patch
@modelcontextprotocol/server-legacy	Patch
@modelcontextprotocol/core-internal	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[arhancanli]

Read the diff against main (static read, I did not run the suite). The existing budget tests in packages/server/test/server/toolInputElementBudget.test.ts only assert toContain('more than the maximum') (lines 63, 97, 128), so they pass with or without the new prefix and nothing pins it. The schema-failure prefix is pinned in mcp.test.ts (stringContaining('Input validation error: Invalid arguments for tool test')), so a one-line assertion on the budget path, e.g. toContain('Input validation error: Invalid arguments for tool') next to the line-63 check, would keep the two paths from drifting apart again. Small nit: the changeset text refers to 'line 374', which will go stale; naming validateToolInput is more durable.