audited Aug 28, 2026in 6s
28/ 100

3 tools registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use48
Usefulness13
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
get_pricing: fail

get_pricing

Get AgentLine pricing details for AI voice calls, phone numbers, and SMS.Registered without an execute function, so calling it does nothing.
pagehttps://agentline.cloud/
implementation
viaimperative
entry pointdocument
registered after1005ms
executemissing
api surfaceTakes no parameters.
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
3 findings
failStub detection
0 / 5
Every registered tool is a facade: none declares an execute handler, so an agent that calls one gets nothing back.
get_pricing, get_features, get_skill_file
fix
{
  name: "get_pricing",
  execute: async (args) => {
    // Perform the real action here - return live data, not a static placeholder.
    return result;
  }
}
failAnnotations present
0 / 4
3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
get_pricing, get_features, get_skill_file
fix
{
  name: "get_pricing",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
3 of 3 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_pricing, get_features, get_skill_file
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_pricing" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_pricing",
  "description": "Get AgentLine pricing details for AI voice calls, phone numbers, and SMS.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {}
}
Showing get_pricing

Findings

WebMCP use

48 / 100 · weight 50
warningTools registered
2 / 4
3 tools registered across 1 page, but not one of the 3 JavaScript tools declares an execute handler, so an agent finds them and can run none of them.
fix
document.modelContext.provideContext({
  tools: [{ name: "your_tool_name", description: "...", inputSchema: { type: "object", properties: {} }, execute: async (args) => { /* ... */ } }],
});
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.
warningRegistration timing
2 / 4
The slowest tool took 1005.0999999046326ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
toolget_features
get_features: registered at 1005.0999999046326ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
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.
passSchema quality
4 / 4
All 3 tool schemas describe their parameters and stay within Chrome's size guidance.
failStub detection
0 / 5
Every registered tool is a facade: none declares an execute handler, so an agent that calls one gets nothing back.
toolget_pricing
get_pricing, get_features, get_skill_file
fix
{
  name: "get_pricing",
  execute: async (args) => {
    // Perform the real action here - return live data, not a static placeholder.
    return result;
  }
}
failAnnotations present
0 / 4
3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolget_pricing
get_pricing, get_features, get_skill_file
fix
{
  name: "get_pricing",
  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
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

13 / 100 · weight 30
passNaming quality
2 / 2
All 3 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.
failTool selection
0 / 14
Not one of the 3 registered tools can be called, so no intent an agent arrives with is servable regardless of which tool it picks.
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
3 of 3 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_pricing
get_pricing, get_features, get_skill_file
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_pricing" 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
3
run time
6s
finished
Aug 28, 2026