audited Aug 28, 2026in 5s
54/ 100

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

WebMCP use74
Usefulness50
Human experience13
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
get_company_profile: fail

get_company_profile

Returns Siblings Software company profile, delivery model, ideal buyers, and contact channels.Takes an action on the site.
pagehttps://siblingssoftware.com.ar/
implementation
viaimperative
entry pointnavigator
registered after723ms
executepresent
api surfaceTakes no parameters.
annotations
read onlynot declared
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: [/* ... */] });
failAnnotations present
0 / 4
7 of 7 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
get_company_profile, list_services, find_service_by_intent, compare_engagement_models, get_case_studies
fix
{
  name: "get_company_profile",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
1 / 8
7 of 8 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_company_profile, list_services, find_service_by_intent, compare_engagement_models, get_case_studies
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_company_profile" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_company_profile",
  "description": "Returns Siblings Software company profile, delivery model, ideal buyers, and contact channels.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {}
}
Showing get_company_profile

Findings

WebMCP use

74 / 100 · weight 50
passTools registered
4 / 4
7 imperative tools and 1 declarative form registered across 1 page.
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 722.9000000953674ms of navigation. 1 further tool carried no measurable registration time.
toollist_services
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_company_profile
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 7 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
4 of 8 tool schemas are harder for an agent to use than they need to be: list_services declares no required list, so an agent cannot tell which parameters are mandatory.
toollist_services
list_services: declares no required list, so an agent cannot tell which parameters are mandatory; compare_engagement_models: declares no required list, so an agent cannot tell which parameters are man
fix
{
  name: "list_services",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 7 tools declare an execute handler.
failAnnotations present
0 / 4
7 of 7 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolget_company_profile
get_company_profile, list_services, find_service_by_intent, compare_engagement_models, get_case_studies
fix
{
  name: "get_company_profile",
  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
7 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: names mix camel and snake conventions; 1 name does not start with a verb (contactSiblingsSoftware).
toolcontactSiblingsSoftware
fix
{ name: "contactsiblingssoftware" /* 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.
warningCoverage vs. site type
4 / 8
The tool set covers 2 of the 4 things an agent needs on a saas site; it cannot create a record or start a job or update or move an existing record.

Human experience

13 / 100 · weight 20
warningHuman parity
1 / 8
7 of 8 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_company_profile
get_company_profile, list_services, find_service_by_intent, compare_engagement_models, get_case_studies
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_company_profile" 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
8
run time
5s
finished
Aug 28, 2026