audited Aug 28, 2026in 4s
49/ 100

7 tools registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use63
Usefulness59
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_cocktails: fail

search_cocktails

Search the cocktail catalogue by name (substring, case- and diacritic-insensitive, so "carre" matches "Carré"). Returns up to 25 summary results — name, page URL, family, glassware — ranked exact match first, then prefix, then suffix, then any substring. Use this when the user names a drink (even fuzzily) and you want to confirm it exists or disambiguate similar names; once you have a single name, call get_cocktail_recipe for the full recipe. For ingredient-based discovery use find_cocktails_by_ingredient instead.Answers a question. Declared read only.
pagehttps://cocktail.glass/
implementation
viaimperative
entry pointnavigator
registered after228ms
executepresent
api surface
queryrequired
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldfalse
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
0.6 / 4
6 of 7 tool schemas are harder for an agent to use than they need to be: search_cocktails description is 519 characters, over Chrome's 500-character guidance.
search_cocktails: description is 519 characters, over Chrome's 500-character guidance; list_cocktails: description is 543 characters, over Chrome's 500-character guidance; list_cocktails: 1 parameter 
fix
{
  name: "search_cocktails",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
7 of 7 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_cocktails, list_cocktails, get_cocktail_recipe, find_cocktails_by_ingredient, find_cocktails_in_movie
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_cocktails" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_cocktails",
  "description": "Search the cocktail catalogue by name (substring, case- and diacritic-insensitive, so \"carre\" matches \"Carré\"). Returns up to 25 summary results — name, page URL, family, glassware — ranked exact match first, then prefix, then suffix, then any substring. Use this when the user names a drink (even fuzzily) and you want to confirm it exists or disambiguate similar names; once you have a single name, call get_cocktail_recipe for the full recipe. For ingredient-based discovery use find_cocktails_by_ingredient instead.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "minLength": 1,
        "description": "Cocktail name or part of one — a single drink name, not an ingredient or category.",
        "examples": [
          "Negroni",
          "margarita",
          "carre"
        ]
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}
Showing search_cocktails

Findings

WebMCP use

63 / 100 · weight 50
passTools registered
4 / 4
7 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 228ms of navigation.
toolrandom_cocktail
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_cocktails
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 7 tools declare a structurally valid object input schema.
warningSchema quality
0.6 / 4
6 of 7 tool schemas are harder for an agent to use than they need to be: search_cocktails description is 519 characters, over Chrome's 500-character guidance.
toolsearch_cocktails
search_cocktails: description is 519 characters, over Chrome's 500-character guidance; list_cocktails: description is 543 characters, over Chrome's 500-character guidance; list_cocktails: 1 parameter 
fix
{
  name: "search_cocktails",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 7 tools declare an execute handler.
passAnnotations present
4 / 4
All 7 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 (7 declared hints checked).
not applicableUntrusted content hint
0 / 2
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
7 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

59 / 100 · weight 30
warningNaming quality
1.9 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (random_cocktail).
toolrandom_cocktail
fix
{ name: "random_cocktail" /* 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.
warningCoverage vs. site type
4 / 8
The tool set covers 2 of the 4 things an agent needs on a commerce site; it cannot add to or read the cart or start checkout or place an order.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
7 of 7 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_cocktails
search_cocktails, list_cocktails, get_cocktail_recipe, find_cocktails_by_ingredient, find_cocktails_in_movie
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_cocktails" 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
7
run time
4s
finished
Aug 28, 2026