worldmonitor.app WebMCP audit

Rescan
audited Aug 28, 2026in 5s
69/ 100

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

WebMCP use93
Usefulness75
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
launchWorldMonitor: warning

launchWorldMonitor

Open the live World Monitor intelligence dashboard in this tab. Optionally choose a specialized monitor variant (world, tech, finance, commodity, energy, happy). Navigates to the real-time map — conflicts, markets, shipping chokepoints, flights and cyber on one surface.Takes an action on the site.
pagehttps://www.worldmonitor.app/
implementation
viaimperative
entry pointdocument
registered after187ms
executepresent
api surface
monitoroptional
annotations
read onlyfalse
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
3 findings
warningSchema quality
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: launchWorldMonitor declares no required list, so an agent cannot tell which parameters are mandatory.
launchWorldMonitor: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "launchWorldMonitor",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningNaming quality
1.5 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (launchWorldMonitor).
fix
{ name: "launchworldmonitor" /* short, unique, verb-based */ }
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.
launchWorldMonitor, getWorldMonitorMcpEndpoint
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="launchworldmonitor" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "launchWorldMonitor",
  "description": "Open the live World Monitor intelligence dashboard in this tab. Optionally choose a specialized monitor variant (world, tech, finance, commodity, energy, happy). Navigates to the real-time map — conflicts, markets, shipping chokepoints, flights and cyber on one surface.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "monitor": {
        "type": "string",
        "enum": [
          "world",
          "tech",
          "finance",
          "commodity",
          "energy",
          "happy"
        ],
        "description": "Which monitor to open. Defaults to \"world\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false
  }
}
Showing launchWorldMonitor

Findings

WebMCP use

93 / 100 · weight 50
passTools registered
4 / 4
2 tools registered across 1 page.
passReal-browser eligible
8 / 8
A real browser exposes modelContext natively on this page, so the tools registered here are visible to an agent today.
passRegistration timing
4 / 4
Every measured tool registered within 187ms of navigation.
toolgetWorldMonitorMcpEndpoint
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.
warningSchema quality
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: launchWorldMonitor declares no required list, so an agent cannot tell which parameters are mandatory.
toollaunchWorldMonitor
launchWorldMonitor: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "launchWorldMonitor",
  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).
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
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

75 / 100 · weight 30
warningNaming quality
1.5 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (launchWorldMonitor).
toollaunchWorldMonitor
fix
{ name: "launchworldmonitor" /* 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

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