plori.ai WebMCP audit

audited Aug 28, 2026in 4s
58/ 100

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

WebMCP use78
Usefulness50
Human experience20
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
plori_get_capabilities: warning

plori_get_capabilities

Describe what plori offers and where an external agent can connect for the complete tool set.Answers a question. Declared read only.
pagehttps://plori.ai/
implementation
viaimperative
entry pointdocument
registered after263ms
executepresent
api surfaceTakes no parameters.
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
2 findings
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 5 names do not start with a verb (plori_get_capabilities).
fix
{ name: "plori_get_capabilities" /* short, unique, verb-based */ }
warningHuman parity
1.6 / 8
4 of 5 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.
plori_get_capabilities, plori_get_mcp_connection, plori_list_examples, plori_open_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="plori_get_capabilities" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "plori_get_capabilities",
  "description": "Describe what plori offers and where an external agent can connect for the complete tool set.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing plori_get_capabilities

Findings

WebMCP use

78 / 100 · weight 50
passTools registered
4 / 4
4 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 262.59999990463257ms of navigation. 1 further tool carried no measurable registration time.
toolplori_get_mcp_connection
passCanonical entry point
4 / 4
All 4 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 4 tools declare a structurally valid object input schema.
passSchema quality
4 / 4
All 5 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 4 tools declare an execute handler.
warningAnnotations present
3 / 4
1 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolplori_open_page
plori_open_page
fix
{
  name: "plori_open_page",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
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
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

50 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 5 names do not start with a verb (plori_get_capabilities).
toolplori_get_capabilities
fix
{ name: "plori_get_capabilities" /* 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

20 / 100 · weight 20
warningHuman parity
1.6 / 8
4 of 5 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.
toolplori_get_capabilities
plori_get_capabilities, plori_get_mcp_connection, plori_list_examples, plori_open_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="plori_get_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
5
run time
4s
finished
Aug 28, 2026