lirn.net WebMCP audit

Name: lirn.net WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 5s

55/ 100

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

WebMCP use67

Usefulness50

Human experience33

about:blank

No agent run recorded yet.

No steps recorded

Tools

search_site

Search all static articles, blogs, and documentation on this site using keywords.Takes an action on the site.

pagehttps://www.lirn.net/

implementation

viaimperative

entry pointdocument

registered after331ms

executepresent

api surface

queryrequired

annotations

read onlynot declared

destructivenot declared

idempotentnot declared

open worldnot declared

untrusted contentnot declared

titlenot declared

3 findings

passRegistration timing

4 / 4

Every measured tool registered within 331.60000014305115ms of navigation. 1 further tool carried no measurable registration time.

failAnnotations present

0 / 4

2 of 2 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

search_site, search_site

fix

{
  name: "search_site",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

warningHuman parity

2.7 / 8

2 of 3 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_site, search_site

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_site" tooldescription="...">
  <!-- the same action, as UI -->
</form>

tool json

{
  "name": "search_site",
  "description": "Search all static articles, blogs, and documentation on this site using keywords.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "The search keyword or phrase."
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}

Findings

WebMCP use

67 / 100 · weight 50

passTools registered

4 / 4

2 imperative tools and 1 declarative form 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 1 declarative form tool on the page stay usable regardless.

passRegistration timing

4 / 4

Every measured tool registered within 331.60000014305115ms of navigation. 1 further tool carried no measurable registration time.

toolsearch_site

passCanonical entry point

4 / 4

All 2 tools register on the canonical document.modelContext entry point.

passSchema validity

5 / 5

All 2 tools declare a structurally valid object input schema.

passSchema quality

4 / 4

All 3 tool schemas describe their parameters and stay within Chrome's size guidance.

passStub detection

5 / 5

All 2 tools declare an execute handler.

failAnnotations present

0 / 4

2 of 2 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

toolsearch_site

search_site, search_site

fix

{
  name: "search_site",
  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.

warningRegistration errors

1 / 2

1 tool registration threw during the capture, so the registry an agent reads is incomplete.

duplicate tool name registered: search_site

fix

try {
  document.modelContext.provideContext({ tools: [/* ... */] });
} catch (err) {
  console.error("WebMCP registration failed", err);
}

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

50 / 100 · weight 30

warningNaming quality

1 / 2

Tool naming makes selection harder than it needs to be: names mix camel and snake conventions.

fix

{ name: "your_tool_name" /* 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.

not applicableCoverage vs. site type

0 / 8

This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

33 / 100 · weight 20

warningHuman parity

2.7 / 8

toolsearch_site

search_site, search_site

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_site" 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: 3
run time: 5s
finished: Aug 28, 2026