doodleduo.prompthabbit.com WebMCP audit

Name: doodleduo.prompthabbit.com WebMCP audit
Creator: ora

Rescan

audited Sep 1, 2026in 11s

66/ 100100% of the applicable check weight evaluated

6 tools registered. Strongest in shared experience, weakest in task completion.

Shared experience100

Task completion13

Tool quality83

Trust60

https://doodleduo.prompthabbit.com

Tools

2 read, 0 write, 4 undeclared

Loading map

doodle_join

Join Doodle Duo as the human’s AI partner. Stops the demo and resets the match to round one. Only call once, then inspect state.No behaviour hints declared. Agents should treat it as possibly state-changing.

pagehttps://doodleduo.prompthabbit.com/

implementation

viaimperative

entry pointdocument

registered after158ms

executepresent

api surface

nameoptional

annotations

read onlynot declared

untrusted contentnot declared

titlenot declared

3 findings

warningSchema quality

weight 4

5 of 6 tool schemas are harder for an agent to use than they need to be: doodle_join 1 parameter has no description (name).

doodle_join: 1 parameter has no description (name); doodle_get_canvas: 1 parameter has no description (includeStrokes); doodle_draw: 1 parameter has no description (strokes); doodle_guess: 1 parameter

fix

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

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (doodle_join).

fix

{ name: "doodle_join" /* short, unique, verb-based */ }

warningInjection surface

weight 4

4 of 6 tools carry instruction-shaped text in their own metadata: doodle_join Description instructs agent how to behave.

doodle_join: Description instructs agent how to behave; doodle_get_state: Description instructs agent when to call and how to behave; doodle_get_canvas: Description instructs agent what to observe and what not to observe; doodle_draw: Description instructs agent how to draw

fix

{
  name: "doodle_join",
  // 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": "doodle_join",
  "description": "Join Doodle Duo as the human’s AI partner. Stops the demo and resets the match to round one. Only call once, then inspect state.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 24
      }
    },
    "required": [],
    "additionalProperties": false
  },
  "annotations": {}
}

Findings

Shared experience

100 / 100 · weight 30

passPage experience

weight 20

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 10

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

Task completion

13 / 100 · weight 25

failTool selection

weight 15

An agent chose an existing tool and built a schema-valid call that held up on 0 of 3 canonical intents; on "Open the document I was working on most recently." no tool on the page served it. Nothing was executed, so this verifies selection, not outcomes.

failCoverage vs. site type

weight 10

The tool set covers 1 of the 3 things an agent needs on a editor site; it cannot edit or write content or save, publish, or share the result.

Tool quality

83 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 158ms of navigation.

tooldoodle_guess

passCanonical entry point

weight 3

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

passSchema validity

weight 4

All 6 declared input schemas are structurally valid object schemas.

warningSchema quality

weight 4

5 of 6 tool schemas are harder for an agent to use than they need to be: doodle_join 1 parameter has no description (name).

tooldoodle_join

doodle_join: 1 parameter has no description (name); doodle_get_canvas: 1 parameter has no description (includeStrokes); doodle_draw: 1 parameter has no description (strokes); doodle_guess: 1 parameter

fix

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

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (doodle_join).

tooldoodle_join

fix

{ name: "doodle_join" /* short, unique, verb-based */ }

passStub detection

weight 4

All 6 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

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

Trust

60 / 100 · weight 20

not applicableAnnotations present

weight 6

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 6

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

not applicableUntrusted content hint

weight 4

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

warningInjection surface

weight 4

4 of 6 tools carry instruction-shaped text in their own metadata: doodle_join Description instructs agent how to behave.

tooldoodle_join

doodle_join: Description instructs agent how to behave; doodle_get_state: Description instructs agent when to call and how to behave; doodle_get_canvas: Description instructs agent what to observe and what not to observe; doodle_draw: Description instructs agent how to draw

fix

{
  name: "doodle_join",
  // 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

0% across 3 intents

Open the document I was working on most recently.missed

choseno toolexpected document openkind not applicable

No tool was picked for this intent.

arguments

{}

Add a short summary paragraph at the top.missed

choseno toolexpected content editkind not applicable

No tool was picked for this intent.

arguments

{}

Save it and give me a link I can share.missed

choseno toolexpected save or sharekind not applicable

No tool was picked for this intent.

arguments

{}

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 148.0.7778.96)
chrome: 148.0.7778.96
capture shim: v1
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 6
run time: 11s
finished: Sep 1, 2026

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