store.tryrankly.com WebMCP audit

Rescan
audited Aug 28, 2026in 5s
60/ 100

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

WebMCP use63
Usefulness94
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_products: fail

search_products

Search the Rankly Merch catalog. Returns up to `limit` products matching the query and/or category. Each result includes slug (use it with get_product or navigate), name, color, priceCents, and stock summary.Answers a question. Declared read only.
pagehttps://store.tryrankly.com/
implementation
viaimperative
entry pointnavigator
registered after428ms
executepresent
api surface
queryoptional
categoryoptional
limitoptional
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
3 findings
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
warningSchema quality
1.7 / 4
8 of 14 tool schemas are harder for an agent to use than they need to be: search_products 1 parameter has no description (limit).
search_products: 1 parameter has no description (limit); get_product: 2 parameters have no description (slug, name); best_sellers: 2 parameters have no description (category, limit); find_deals: 2 par
fix
{
  name: "search_products",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
14 of 14 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_products, get_product, list_categories, best_sellers, find_deals
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_products" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_products",
  "description": "Search the Rankly Merch catalog. Returns up to `limit` products matching the query and/or category. Each result includes slug (use it with get_product or navigate), name, color, priceCents, and stock summary.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Free-text search across name, description, tags, category."
      },
      "category": {
        "type": "string",
        "description": "Category slug. Use list_categories to discover valid values."
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 50,
        "default": 12
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing search_products

Findings

WebMCP use

63 / 100 · weight 50
passTools registered
4 / 4
14 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.
passRegistration timing
4 / 4
Every measured tool registered within 428.10000014305115ms of navigation.
toolsign_in
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolsearch_products
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 14 tools declare a structurally valid object input schema.
warningSchema quality
1.7 / 4
8 of 14 tool schemas are harder for an agent to use than they need to be: search_products 1 parameter has no description (limit).
toolsearch_products
search_products: 1 parameter has no description (limit); get_product: 2 parameters have no description (slug, name); best_sellers: 2 parameters have no description (category, limit); find_deals: 2 par
fix
{
  name: "search_products",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 14 tools declare an execute handler.
passAnnotations present
4 / 4
All 14 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 (14 declared hints checked).
warningUntrusted content hint
0 / 2
2 of 2 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.
toolplace_demo_order
place_demo_order: user, email; authenticate: profile, user
fix
{ name: "place_demo_order", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
14 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

94 / 100 · weight 30
warningNaming quality
1.4 / 2
Tool naming makes selection harder than it needs to be: 8 names do not start with a verb (best_sellers).
toolbest_sellers
fix
{ name: "best_sellers" /* 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
14 of 14 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_products
search_products, get_product, list_categories, best_sellers, find_deals
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_products" 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
14
run time
5s
finished
Aug 28, 2026