audited Aug 28, 2026in 7s
63/ 100

10 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use67
Usefulness98
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_catalog: warning

search_catalog

Search the store catalog for products, collections, articles, and pages. Does NOT add anything to the cart; use update_cart for cart changes. If the user asks for a specific product variant, call get_product after search_catalog to inspect available variants, then show_variant to display one.Answers a question. Declared read only.
pagehttps://www.lisaraleigh.com/
implementation
viaimperative
entry pointdocument
registered after1014ms
executepresent
api surface
catalogrequired
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contenttrue
titlenot declared
2 findings
warningSchema quality
1.6 / 4
6 of 10 tool schemas are harder for an agent to use than they need to be: search_catalog 1 parameter has no description (catalog).
search_catalog: 1 parameter has no description (catalog); browse_store: description is 891 characters, over Chrome's 500-character guidance; browse_store: 2 parameter descriptions are over Chrome's 15
fix
{
  name: "search_catalog",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
10 of 10 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
search_catalog, browse_store, get_product, show_variant, get_cart
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_catalog" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_catalog",
  "description": "Search the store catalog for products, collections, articles, and pages. Does NOT add anything to the cart; use update_cart for cart changes. If the user asks for a specific product variant, call get_product after search_catalog to inspect available variants, then show_variant to display one.",
  "inputSchema": {
    "type": "object",
    "required": [
      "catalog"
    ],
    "properties": {
      "catalog": {
        "type": "object",
        "required": [
          "query"
        ],
        "properties": {
          "query": {
            "type": "string",
            "description": "Search query string."
          },
          "pagination": {
            "type": "object",
            "properties": {
              "limit": {
                "type": "integer",
                "description": "Max results per type (1-10). Defaults to 5.",
                "default": 5,
                "minimum": 1,
                "maximum": 10
              }
            }
          }
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": true,
    "untrustedContentHint": true
  }
}
Showing search_catalog

Findings

WebMCP use

67 / 100 · weight 50
passTools registered
4 / 4
10 tools registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither. The page does carry an origin-trial token, but it does not grant WebMCP on this origin.
warningRegistration timing
2 / 4
The slowest tool took 1013.9000000953674ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
toolmanage_orders
manage_orders: registered at 1013.9000000953674ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
passCanonical entry point
4 / 4
All 10 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 10 tools declare a structurally valid object input schema.
warningSchema quality
1.6 / 4
6 of 10 tool schemas are harder for an agent to use than they need to be: search_catalog 1 parameter has no description (catalog).
toolsearch_catalog
search_catalog: 1 parameter has no description (catalog); browse_store: description is 891 characters, over Chrome's 500-character guidance; browse_store: 2 parameter descriptions are over Chrome's 15
fix
{
  name: "search_catalog",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 10 tools declare an execute handler.
passAnnotations present
4 / 4
All 10 tools declare a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (10 declared hints checked).
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolmanage_orders
manage_orders: user, customer
fix
{ name: "manage_orders", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
10 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

98 / 100 · weight 30
warningNaming quality
1.8 / 2
Tool naming makes selection harder than it needs to be: 2 names do not start with a verb (proceed_to_checkout).
toolproceed_to_checkout
fix
{ name: "proceed_to_checkout" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
passCoverage vs. site type
8 / 8
The tool set covers the whole core commerce flow: search or browse the catalog, read one item in detail, add to or read the cart, start checkout or place an order.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
10 of 10 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolsearch_catalog
search_catalog, browse_store, get_product, show_variant, get_cart
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_catalog" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
10
run time
7s
finished
Aug 28, 2026