match-ai.nl WebMCP audit

audited Aug 28, 2026in 5s
65/ 100

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

WebMCP use70
Usefulness100
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/nl
get_match_ai_services: warning

get_match_ai_services

Geeft een overzicht van publieke Match-AI diensten en landingspagina’s.Answers a question. Declared read only.
pagehttps://match-ai.nl/nl
implementation
viaimperative
entry pointprovideContext
registered after306ms
executepresent
api surface
languageoptional
annotations
read onlytrue
destructivefalse
idempotentnot declared
open worldfalse
untrusted contentnot declared
titlenot declared
2 findings
warningSchema quality
2 / 4
5 of 10 tool schemas are harder for an agent to use than they need to be: get_match_ai_services 1 parameter has no description (language).
get_match_ai_services: 1 parameter has no description (language); get_match_ai_proposition: 1 parameter has no description (language); recommend_match_ai_use_cases: 4 parameters have no description (i
fix
{
  name: "get_match_ai_services",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
10 of 10 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.
get_match_ai_services, get_match_ai_proposition, recommend_match_ai_use_cases, get_match_ai_knowledge_links, start_match_ai_intake
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_match_ai_services" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_match_ai_services",
  "description": "Geeft een overzicht van publieke Match-AI diensten en landingspagina’s.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "language": {
        "type": "string",
        "enum": [
          "nl",
          "en",
          "de"
        ]
      }
    }
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "openWorldHint": false
  }
}
Showing get_match_ai_services

Findings

WebMCP use

70 / 100 · weight 50
passTools registered
4 / 4
10 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 306.80000019073486ms of navigation.
toolstart_match_ai_intake
passCanonical entry point
4 / 4
All 10 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 10 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
5 of 10 tool schemas are harder for an agent to use than they need to be: get_match_ai_services 1 parameter has no description (language).
toolget_match_ai_services
get_match_ai_services: 1 parameter has no description (language); get_match_ai_proposition: 1 parameter has no description (language); recommend_match_ai_use_cases: 4 parameters have no description (i
fix
{
  name: "get_match_ai_services",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 10 tools declare an execute handler.
passAnnotations present
4 / 4
All 10 tools declare a readOnlyHint, so an agent knows which calls change state.
warningAnnotation mismatch
2.4 / 3
2 tools declare readOnlyHint: true although the name says the call writes (start_match_ai_intake).
toolstart_match_ai_intake
start_match_ai_intake: readOnlyHint=true; start_match_ai_intake: readOnlyHint=true
fix
// Set destructiveHint/idempotentHint to match what this tool actually does.
{ name: "start_match_ai_intake", annotations: { destructiveHint: true } }
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.
failRegistration errors
0 / 2
10 tool registrations threw during the capture, so the registry an agent reads is incomplete.
duplicate tool name registered: get_match_ai_services
fix
try {
  document.modelContext.provideContext({ tools: [/* ... */] });
} catch (err) {
  console.error("WebMCP registration failed", err);
}
warningToolchange coherence
1 / 2
10 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 10 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
10 of 10 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.
toolget_match_ai_services
get_match_ai_services, get_match_ai_proposition, recommend_match_ai_use_cases, get_match_ai_knowledge_links, start_match_ai_intake
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_match_ai_services" 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
10
run time
5s
finished
Aug 28, 2026