Repository navigation
core(webmcp-registered-tools): warn when exceeding recommended limit - #17221
Conversation
|
@lusayaa WDYT? |
|
I think it's a good idea, we need to find a reasonable "limit"; Also referencing my comment here: webmachinelearning/webmcp#293 (comment) |
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. |
|
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 . |
connorjclark
left a comment
There was a problem hiding this comment.
A warning is the right construct. I left a comment on the message text.
I've addressed your feedback. Thanks! |
|
Thanks! |
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.