Skip to content

core(webmcp-registered-tools): warn when exceeding recommended limit - #17221

Merged
connorjclark merged 3 commits into
GoogleChrome:mainfrom
beaufortfrancois:max-tools
Sep 16, 2026
Merged

connorjclark merged 3 commits into
GoogleChrome:mainfrom
beaufortfrancois:max-tools

Conversation

@beaufortfrancois

Copy link
Copy Markdown
Member

Following WebMCP spec discussion at webmachinelearning/webmcp#293 (comment), we thought we should have a warning when WebMCP tools exceed a recommended limit. It's 40 in this current PR but there's no hard number.

image

@beaufortfrancois
beaufortfrancois requested a review from a team as a code owner September 4, 2026 13:17
@beaufortfrancois
beaufortfrancois requested review from paulirish and removed request for a team September 4, 2026 13:17
@beaufortfrancois beaufortfrancois changed the title feat: add audit warning when WebMCP tools exceed recommended limit of 40 new_audit: add warning when WebMCP tools exceed recommended limit Sep 4, 2026
@beaufortfrancois

Copy link
Copy Markdown
Member Author

@lusayaa WDYT?

@Kulikowski

Kulikowski commented Sep 4, 2026 •

Copy link
Copy Markdown

I think it's a good idea, we need to find a reasonable "limit";

Also referencing my comment here: webmachinelearning/webmcp#293 (comment)

@lusayaa

lusayaa commented Sep 4, 2026 •

Copy link
Copy Markdown
Collaborator

@lusayaa WDYT?

Adding a warning for too many tools makes sense in principle. How many of these do you expect will come from 1st party vs 3rd party?

From a lighthouse perspective, I'm not sure if warnings is the canonical way to do this or if it should be its own audit. @connorjclark for input.

@lusayaa

lusayaa commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Makes sense to add a warning. Wondering where the 40 comes from, are there specific metrics that show 40 is where it falls off?

@beaufortfrancois

Copy link
Copy Markdown
Member Author

Makes sense to add a warning. Wondering where the 40 comes from, are there specific metrics that show 40 is where it falls off?

Real-world feedback from modelcontextprotocol/modelcontextprotocol#1251 and architectural deep dives on the MCPOrbit Blog seem to indicate that 40 tools is a performance cliff for LLMs .

Comment thread core/audits/webmcp-registered-tools.js Resolved

@connorjclark connorjclark left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A warning is the right construct. I left a comment on the message text.

@beaufortfrancois

Copy link
Copy Markdown
Member Author

A warning is the right construct. I left a comment on the message text.

I've addressed your feedback. Thanks!

@connorjclark connorjclark changed the title new_audit: add warning when WebMCP tools exceed recommended limit new_audit(webmcp-registered-tools): warn when tools exceed recommended limit Sep 16, 2026
@connorjclark connorjclark changed the title new_audit(webmcp-registered-tools): warn when tools exceed recommended limit core(webmcp-registered-tools): warn when tools exceed recommended limit Sep 16, 2026
@connorjclark connorjclark changed the title core(webmcp-registered-tools): warn when tools exceed recommended limit core(webmcp-registered-tools): warn when exceeding recommended limit Sep 16, 2026
@connorjclark
connorjclark merged commit 912e85f into GoogleChrome:main Sep 16, 2026
32 of 33 checks passed
@connorjclark

Copy link
Copy Markdown
Collaborator

Thanks!

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.

4 participants