notte.cc WebMCP audit

audited Aug 28, 2026in 5s
36/ 100

One tool registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use50
Usefulness37
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
openDocs: fail

openDocs

Open Notte documentation for a given topic (e.g. 'quickstart', 'concepts/agents'). Defaults to the docs homepage if no topic is given.Takes an action on the site.
pagehttps://www.notte.cc/
implementation
viaimperative
entry pointnavigator
registered after893ms
executepresent
api surface
topicoptional
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
6 findings
passRegistration timing
4 / 4
Every measured tool registered within 892.5ms of navigation.
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 / 4
1 of 1 tool schemas are harder for an agent to use than they need to be: openDocs declares no required list, so an agent cannot tell which parameters are mandatory.
openDocs: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "openDocs",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (openDocs).
fix
{ name: "opendocs" /* short, unique, verb-based */ }
failAnnotations present
0 / 4
1 of 1 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
openDocs
fix
{
  name: "openDocs",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
1 of 1 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.
openDocs
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="opendocs" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "openDocs",
  "description": "Open Notte documentation for a given topic (e.g. 'quickstart', 'concepts/agents'). Defaults to the docs homepage if no topic is given.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "topic": {
        "type": "string",
        "description": "Docs slug or keyword appended to https://docs.notte.cc/. Omit for the docs homepage."
      }
    }
  },
  "annotations": {}
}
Showing openDocs

Findings

WebMCP use

50 / 100 · weight 50
passTools registered
4 / 4
1 tool 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 892.5ms of navigation.
toolopenDocs
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolopenDocs
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 1 tool declare a structurally valid object input schema.
warningSchema quality
0 / 4
1 of 1 tool schemas are harder for an agent to use than they need to be: openDocs declares no required list, so an agent cannot tell which parameters are mandatory.
toolopenDocs
openDocs: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "openDocs",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
The one registered tool declares an execute handler.
failAnnotations present
0 / 4
1 of 1 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolopenDocs
openDocs
fix
{
  name: "openDocs",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
not applicableAnnotation mismatch
0 / 3
No tool declares a readOnlyHint, so there is no safety claim to contradict.
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
1 tool was 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

37 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (openDocs).
toolopenDocs
fix
{ name: "opendocs" /* 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.
failCoverage vs. site type
2.7 / 8
The tool set covers 1 of the 3 things an agent needs on a docs site; it cannot search or browse the catalog or navigate the documentation tree.

Human experience

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