seiright.com WebMCP audit

Rescan
audited Aug 28, 2026in 8s
50/ 100

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

WebMCP use71
Usefulness40
Human experience14
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
get_platform_capabilities: fail

get_platform_capabilities

Get the three core capabilities of the Sei AI platform: voice agents, document intelligence, and call monitoring & compliance. Use this to answer questions about what Sei does.Takes an action on the site.
pagehttps://www.seiright.com/
implementation
viaimperative
entry pointnavigator
registered after699ms
executepresent
api surfaceTakes no parameters.
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
4 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: [/* ... */] });
failSchema validity
1.7 / 5
4 of 6 tools declare an input schema an agent cannot read: get_platform_capabilities declares no input schema.
get_platform_capabilities: declares no input schema; get_case_studies: declares no input schema; get_security_info: declares no input schema; get_company_info: declares no input schema
fix
{
  name: "get_platform_capabilities",
  inputSchema: { type: "object", properties: { /* ... */ }, required: [] }
}
failAnnotations present
0 / 4
6 of 6 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
get_platform_capabilities, get_capability_details, get_case_studies, get_security_info, get_company_info
fix
{
  name: "get_platform_capabilities",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
1.1 / 8
6 of 7 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_platform_capabilities, get_capability_details, get_case_studies, get_security_info, get_company_info
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_platform_capabilities" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_platform_capabilities",
  "description": "Get the three core capabilities of the Sei AI platform: voice agents, document intelligence, and call monitoring & compliance. Use this to answer questions about what Sei does.",
  "inputSchema": null,
  "annotations": {}
}
Showing get_platform_capabilities

Findings

WebMCP use

71 / 100 · weight 50
passTools registered
4 / 4
6 imperative tools and 1 declarative form registered across 1 page. Capture caveat (not scored against the site): the page replaced modelContext on navigator, so imperative tools may be under-reported
passReal-browser eligible
8 / 8
A real browser exposes modelContext natively on this page, so the tools registered here are visible to an agent today.
passRegistration timing
4 / 4
Every measured tool registered within 700.2999999523163ms of navigation. 1 further tool carried no measurable registration time.
toolread_page
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolget_platform_capabilities
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
failSchema validity
1.7 / 5
4 of 6 tools declare an input schema an agent cannot read: get_platform_capabilities declares no input schema.
toolget_platform_capabilities
get_platform_capabilities: declares no input schema; get_case_studies: declares no input schema; get_security_info: declares no input schema; get_company_info: declares no input schema
fix
{
  name: "get_platform_capabilities",
  inputSchema: { type: "object", properties: { /* ... */ }, required: [] }
}
passSchema quality
4 / 4
All 7 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 6 tools declare an execute handler.
failAnnotations present
0 / 4
6 of 6 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolget_platform_capabilities
get_platform_capabilities, get_capability_details, get_case_studies, get_security_info, get_company_info
fix
{
  name: "get_platform_capabilities",
  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. Capture caveat (not scored against the site): the page replaced modelContext on navigator, so imperative tools may be under-reported
warningToolchange coherence
1 / 2
6 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

40 / 100 · weight 30
passNaming quality
2 / 2
All 7 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.
failCoverage vs. site type
2 / 8
The tool set covers 1 of the 4 things an agent needs on a saas site; it cannot search or browse the catalog or create a record or start a job or update or move an existing record.

Human experience

14 / 100 · weight 20
warningHuman parity
1.1 / 8
6 of 7 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_platform_capabilities
get_platform_capabilities, get_capability_details, get_case_studies, get_security_info, get_company_info
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_platform_capabilities" 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
7
run time
8s
finished
Aug 28, 2026