heroleague.ai WebMCP audit

audited Aug 28, 2026in 7s
56/ 100

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

WebMCP use60
Usefulness88
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
list_questions: fail

list_questions

List HAIL assessment questions for simple, professional, or advanced profile. Advanced (real-number telemetry) is always available — no Premium required. Each question includes tier (core|extended) and core_position. Payload also returns core_count, core_keys, and extended_order.Answers a question. Declared read only.
pagehttps://heroleague.ai/
implementation
viaimperative
entry pointnavigator
registered after834ms
executepresent
api surface
profileoptional
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
3 findings
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
warningSchema quality
0 / 4
4 of 4 tool schemas are harder for an agent to use than they need to be: list_questions 1 parameter has no description (profile).
list_questions: 1 parameter has no description (profile); run_assessment: 6 parameters have no description (email, team_name, profile, answers); get_result: 1 parameter has no description (run_id); ge
fix
{
  name: "list_questions",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningHuman parity
0 / 8
4 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.
list_questions, run_assessment, get_result, get_playbook
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="list_questions" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "list_questions",
  "description": "List HAIL assessment questions for simple, professional, or advanced profile. Advanced (real-number telemetry) is always available — no Premium required. Each question includes tier (core|extended) and core_position. Payload also returns core_count, core_keys, and extended_order.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "profile": {
        "type": "string",
        "enum": [
          "simple",
          "professional",
          "advanced"
        ]
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing list_questions

Findings

WebMCP use

60 / 100 · weight 50
passTools registered
4 / 4
4 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 834.5ms of navigation.
toolrun_assessment
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toollist_questions
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 4 tools declare a structurally valid object input schema.
warningSchema quality
0 / 4
4 of 4 tool schemas are harder for an agent to use than they need to be: list_questions 1 parameter has no description (profile).
toollist_questions
list_questions: 1 parameter has no description (profile); run_assessment: 6 parameters have no description (email, team_name, profile, answers); get_result: 1 parameter has no description (run_id); ge
fix
{
  name: "list_questions",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 4 tools declare an execute handler.
passAnnotations present
4 / 4
All 4 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 (4 declared hints checked).
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolrun_assessment
run_assessment: profile, email
fix
{ name: "run_assessment", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
4 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

88 / 100 · weight 30
warningNaming quality
1.8 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (run_assessment).
toolrun_assessment
fix
{ name: "run_assessment" /* short, unique, verb-based */ }
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
4 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.
toollist_questions
list_questions, run_assessment, get_result, get_playbook
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="list_questions" 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
7s
finished
Aug 28, 2026