audited Aug 28, 2026in 7s
59/ 100

One tool registered. Strongest in usefulness, weakest in human experience.

WebMCP use58
Usefulness100
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
get_friendly_guid: fail

get_friendly_guid

Get a FriendlyGUID. Optionally provide a memorable seed word or phrase; FriendlyGUID converts it to a valid GUID/UUID and can update the page.Takes an action on the site.
pagehttps://www.friendlyguid.com/#aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
implementation
viaimperative
entry pointnavigator
registered after1079ms
executepresent
api surface
seedoptional
uppercaseoptional
updatePageoptional
annotations
read onlyfalse
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
4 findings
warningRegistration timing
2 / 4
The slowest tool took 1079ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
get_friendly_guid: registered at 1079ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
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: get_friendly_guid 1 parameter description is over Chrome's 150-character guidance.
get_friendly_guid: 1 parameter description is over Chrome's 150-character guidance
fix
{
  name: "get_friendly_guid",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
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.
get_friendly_guid
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_friendly_guid" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_friendly_guid",
  "description": "Get a FriendlyGUID. Optionally provide a memorable seed word or phrase; FriendlyGUID converts it to a valid GUID/UUID and can update the page.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "seed": {
        "type": "string",
        "description": "Optional memorable word or phrase to convert into a friendly GUID. When omitted, the current page GUID is completed or a new friendly GUID is generated."
      },
      "uppercase": {
        "type": "boolean",
        "description": "Return the GUID in uppercase. Defaults to the page casing setting."
      },
      "updatePage": {
        "type": "boolean",
        "description": "Update the visible FriendlyGUID input with the generated GUID.",
        "default": true
      }
    },
    "required": [],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false
  }
}
Showing get_friendly_guid

Findings

WebMCP use

58 / 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.
warningRegistration timing
2 / 4
The slowest tool took 1079ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
toolget_friendly_guid
get_friendly_guid: registered at 1079ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolget_friendly_guid
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: get_friendly_guid 1 parameter description is over Chrome's 150-character guidance.
toolget_friendly_guid
get_friendly_guid: 1 parameter description is over Chrome's 150-character guidance
fix
{
  name: "get_friendly_guid",
  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.
passAnnotations present
4 / 4
All 1 tool declares 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 (1 declared hint 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
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

100 / 100 · weight 30
passNaming quality
2 / 2
All 1 tool name is 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.
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

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