prompt-commander-dev.vercel.app WebMCP audit

Name: prompt-commander-dev.vercel.app WebMCP audit
Creator: ora

Rescan

audited Sep 10, 2026in 14s

88/ 100100% of the applicable check weight evaluated

One tool registered. Strongest in shared experience, weakest in trust.

Shared experience100

Tool selection100

Tool quality84

Trust62

https://prompt-commander-dev.vercel.app

Tools

1 read, 0 write

Loading map

navigatePromptCommander

Open one of the commander's pages only when they explicitly ask to open, go to, or navigate to it. Do not navigate merely to display or supplement results returned by another tool. Available pages: How to play, Live world, Agent integration guide, Play in the browser.Answers a question. Declared read only.

pagehttps://prompt-commander-dev.vercel.app/

implementation

viaimperative

entry pointdocument

registered after764ms

executepresent

api surface

destinationrequired

annotations

read onlytrue

untrusted contentnot declared

titlenot declared

3 findings

passRegistration timing

weight 1

Every measured tool registered within 764ms of navigation.

warningSchema quality

weight 4

1 of 1 tool schemas are harder for an agent to use than they need to be: navigatePromptCommander 1 parameter has no description (destination).

navigatePromptCommander: 1 parameter has no description (destination)

fix

{
  name: "navigatePromptCommander",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

warningInjection surface

weight 3

1 of 1 tools carry instruction-shaped text in their own metadata: navigatePromptCommander description instructs agent when to use tool and when not to.

navigatePromptCommander: description instructs agent when to use tool and when not to

fix

{
  name: "navigatePromptCommander",
  // Metadata DESCRIBES the tool - it never addresses the agent reading it.
  // Rewrite any name, description, title, or schema field description that
  // instructs the agent (which tool to prefer, what to output, rules to
  // ignore) so it states what the tool does and what it returns instead.
  description: "Searches the catalog and returns matching items with prices."
}

tool json

{
  "name": "navigatePromptCommander",
  "description": "Open one of the commander's pages only when they explicitly ask to open, go to, or navigate to it. Do not navigate merely to display or supplement results returned by another tool. Available pages: How to play, Live world, Agent integration guide, Play in the browser.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "destination": {
        "type": "string",
        "enum": [
          "/how-to-play",
          "/world",
          "/developers",
          "/app"
        ]
      }
    },
    "required": [
      "destination"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Findings

Shared experience

100 / 100 · weight 30

not applicableVisible effect

weight 6

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

passPage experience

weight 16

The page a person sees holds up next to the agent surface: a working interface, visible actions, readable content, nothing in the way.

passHuman parity

weight 8

The person co-browsing can see and use this page - the same page the agent's tools act on.

Tool selection

100 / 100 · weight 25

not applicableInvoke success rate

weight 6

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

passTool selection

weight 12

An agent chose an existing, callable tool and built a schema-valid call for all 1 canonical intents, each matching the kind of tool its intent needs. Nothing was executed, so this verifies selection, not outcomes.

not applicableCoverage vs. site type

weight 7

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.

Tool quality

84 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 764ms of navigation.

toolnavigatePromptCommander

passCanonical entry point

weight 3

The one registered tool registers on the canonical document.modelContext entry point.

passSchema validity

weight 4

All 1 declared input schema is a structurally valid object schema.

warningSchema quality

weight 4

1 of 1 tool schemas are harder for an agent to use than they need to be: navigatePromptCommander 1 parameter has no description (destination).

toolnavigatePromptCommander

navigatePromptCommander: 1 parameter has no description (destination)

fix

{
  name: "navigatePromptCommander",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

passNaming quality

weight 2

All 1 tool name is consistent, verb-led, and within Chrome's size guidance.

passStub detection

weight 4

The one registered tool declares an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

All 1 rated tool descriptions say what the tool does, when to use it, and what it returns.

Trust

62 / 100 · weight 20

not applicableAnnotations present

weight 5

No tool name reads like a read, and an absent readOnlyHint already defaults to "this may write" - the one hint worth declaring here is readOnlyHint: true on read tools, and this set has none to declare it on.

passAnnotation mismatch

weight 5

No tool claims to be read-only while its own name or description says it writes (1 declared hint checked).

not applicableUntrusted content hint

weight 3

No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.

not applicableHint vs. observed

weight 4

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

warningInjection surface

weight 3

1 of 1 tools carry instruction-shaped text in their own metadata: navigatePromptCommander description instructs agent when to use tool and when not to.

toolnavigatePromptCommander

navigatePromptCommander: description instructs agent when to use tool and when not to

fix

{
  name: "navigatePromptCommander",
  // Metadata DESCRIBES the tool - it never addresses the agent reading it.
  // Rewrite any name, description, title, or schema field description that
  // instructs the agent (which tool to prefer, what to output, rules to
  // ignore) so it states what the tool does and what it returns instead.
  description: "Searches the catalog and returns matching items with prices."
}

Tool selection

100% across 1 intents

I want to navigate prompt commander on this site.ok

chosenavigatePromptCommanderexpected navigate prompt commanderkind matched

arguments

{
  "destination": "/how-to-play"
}

model: gemini-2.5-flash

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.

The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.

how this was captured

observed via: capture shim (Chromium 151.0.7922.34)
chrome: 151.0.7922.34
capture shim: v3
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 1
invoked: not invoked; a live audit calls them
run time: 14s
finished: Sep 10, 2026

Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.