Scan at scalePages with undescribed WebMCP tools
Pages with undescribed WebMCP tools
A per-URL report: one row per page that matches, over the pages a crawl reached.
What this report returns
An agent decides whether and how to call a WebMCP tool from its descriptions; an undescribed tool or parameter forces it to guess or skip the tool entirely.
These pages register tools with no tool description, parameters with no usable description, or imperative registerTool calls missing theirs.
The Conformance Issue Detected column separates the two cases: it is true only for the imperative call, where the WebMCP IDL marks description required, and false when the gap is on a declarative form or a parameter, which is Chrome's guidance and Lumar's profile rather than a spec rule.
How to fix it. Add tooldescription / toolparamdescription attributes on declarative forms, and pass description in registerTool, saying what the tool does and when to use it.
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- WebMCP Conformance Issue Detected
webMcpConformanceIssueDetected - WebMCP Findings
webMcpFindings - WebMCP Undescribed Tool Names
webMcpUndescribedToolNames - WebMCP Undescribed Param Names
webMcpUndescribedParamNames - WebMCP Tool Missing Description
webMcpToolMissingDescription - WebMCP Imperative Missing Description
webMcpImperativeMissingDescription - WebMCP Param Missing Description
webMcpParamMissingDescription
About WebMCP
In-page tools a browsing agent can call directly.
Read how WebMCP is checked, including the specification it is validated against and a worked correct and broken example.
Running it
This report ships in the Lumar agent-readiness container and appears on any project it is linked to, on every crawl. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.