attention.com WebMCP audit

Rescan
audited Aug 28, 2026in 7s
54/ 100

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

WebMCP use64
Usefulness73
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
book_demo: fail

book_demo

Navigates to Attention's demo-scheduling page (powered by Default). The page opens a calendar where the user picks a time with the sales team. Optionally pre-fills a note with context (company, team size, use-case).Takes an action on the site.
pagehttps://www.attention.com/
implementation
viaimperative
entry pointnavigator
registered after474ms
executepresent
api surface
noteoptional
annotations
read onlyfalse
destructivefalse
idempotenttrue
open worldtrue
untrusted contentnot declared
titlenot declared
4 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
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: book_demo declares no required list, so an agent cannot tell which parameters are mandatory.
book_demo: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "book_demo",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
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.
book_demo: note, user
fix
{ name: "book_demo", annotations: { untrustedContentHint: true } }
warningHuman parity
0 / 8
2 of 2 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.
book_demo, search_docs
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="book_demo" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "book_demo",
  "description": "Navigates to Attention's demo-scheduling page (powered by Default). The page opens a calendar where the user picks a time with the sales team. Optionally pre-fills a note with context (company, team size, use-case).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "note": {
        "type": "string",
        "description": "Optional context (company name, use-case, team size) to pre-fill on the booking form."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": true
  }
}
Showing book_demo

Findings

WebMCP use

64 / 100 · weight 50
passTools registered
4 / 4
2 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 474.60000014305115ms of navigation.
toolsearch_docs
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolbook_demo
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 2 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: book_demo declares no required list, so an agent cannot tell which parameters are mandatory.
toolbook_demo
book_demo: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "book_demo",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 2 tools declare an execute handler.
passAnnotations present
4 / 4
All 2 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 (2 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.
toolbook_demo
book_demo: note, user
fix
{ name: "book_demo", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
2 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

73 / 100 · weight 30
passNaming quality
2 / 2
All 2 tool names are consistent, verb-led, and within Chrome's size guidance.
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
5.3 / 8
The tool set covers 2 of the 3 things an agent needs on a docs site; it cannot navigate the documentation tree.

Human experience

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