jarrettstanley.com WebMCP audit

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

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

WebMCP use76
Usefulness100
Human experience25
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_content: warning

search_content

Search everything published on jarrettstanley.com - articles on AI in mortgage marketing, glossary definitions, AI tool roundups, campaign teardowns, role playbooks, and Jarrett Stanley's speaking and consulting pages. Returns ranked matches with snippets and canonical URLs.Answers a question. Declared read only.
pagehttps://jarrettstanley.com/
implementation
viaimperative
entry pointdocument
registered after564ms
executepresent
api surface
queryrequired
sectionoptional
limitoptional
annotations
read onlytrue
destructivefalse
idempotenttrue
open worldfalse
untrusted contentnot declared
titlenot declared
2 findings
warningSchema quality
2 / 4
2 of 4 tool schemas are harder for an agent to use than they need to be: search_content 2 parameters have no description (section, limit).
search_content: 2 parameters have no description (section, limit); list_content: 1 parameter has no description (section)
fix
{
  name: "search_content",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
2 / 8
3 of 4 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_content, get_page, list_content
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_content" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_content",
  "description": "Search everything published on jarrettstanley.com - articles on AI in mortgage marketing, glossary definitions, AI tool roundups, campaign teardowns, role playbooks, and Jarrett Stanley's speaking and consulting pages. Returns ranked matches with snippets and canonical URLs.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Search terms, for example \"AI lead scoring\"."
      },
      "section": {
        "type": "string",
        "enum": [
          "all",
          "site",
          "blog",
          "glossary",
          "tools",
          "examples",
          "solutions"
        ],
        "default": "all"
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 25,
        "default": 8
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false
  }
}
Showing search_content

Findings

WebMCP use

76 / 100 · weight 50
passTools registered
4 / 4
3 imperative tools and 1 declarative form 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. The 1 declarative form tool on the page stay usable regardless.
passRegistration timing
4 / 4
Every measured tool registered within 564.1000001430511ms of navigation. 1 further tool carried no measurable registration time.
toolget_page
passCanonical entry point
4 / 4
All 3 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 3 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
2 of 4 tool schemas are harder for an agent to use than they need to be: search_content 2 parameters have no description (section, limit).
toolsearch_content
search_content: 2 parameters have no description (section, limit); list_content: 1 parameter has no description (section)
fix
{
  name: "search_content",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 3 tools declare an execute handler.
passAnnotations present
4 / 4
All 3 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 (3 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
3 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 4 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

25 / 100 · weight 20
warningHuman parity
2 / 8
3 of 4 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_content
search_content, get_page, list_content
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_content" 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
4
run time
5s
finished
Aug 28, 2026