dailybot.com WebMCP audit

audited Aug 28, 2026in 4s
62/ 100

2 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use64
Usefulness100
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_blog: fail

search_blog

Search the dailybot.com blog by keyword. Returns matching blog posts with title, description, slug, publish date, tags, and hero image across English, Spanish, and Portuguese.Takes an action on the site.
pagehttps://www.dailybot.com/
implementation
viaimperative
entry pointprovideContext
registered after407ms
executepresent
api surface
qrequired
langoptional
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 406.89999985694885ms of navigation.
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_blog, search_help
fix
{
  name: "search_blog",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
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.
search_blog, search_help
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_blog" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_blog",
  "description": "Search the dailybot.com blog by keyword. Returns matching blog posts with title, description, slug, publish date, tags, and hero image across English, Spanish, and Portuguese.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "q": {
        "type": "string",
        "description": "Keyword or phrase to search for."
      },
      "lang": {
        "type": "string",
        "enum": [
          "en",
          "es",
          "pt"
        ],
        "description": "Optional language filter. If omitted, the bridge uses the current page language."
      }
    },
    "required": [
      "q"
    ]
  },
  "annotations": {}
}
Showing search_blog

Findings

WebMCP use

64 / 100 · weight 50
passTools registered
4 / 4
2 tools 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.
passRegistration timing
4 / 4
Every measured tool registered within 406.89999985694885ms of navigation.
toolsearch_blog
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: search_help 1 parameter has no description (lang).
toolsearch_help
search_help: 1 parameter has no description (lang)
fix
{
  name: "search_help",
  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.
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_blog
search_blog, search_help
fix
{
  name: "search_blog",
  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.
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

100 / 100 · weight 30
passNaming quality
2 / 2
All 2 tool names are 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
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.
toolsearch_blog
search_blog, search_help
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_blog" 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
4s
finished
Aug 28, 2026