audited Aug 28, 2026in 3s
49/ 100

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

WebMCP use81
Usefulness30
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
admintoolkit_check_ai_crawler_access: warning

admintoolkit_check_ai_crawler_access

Return a read-only RFC 9309 robots.txt access report for AI and search crawlers. Accepts robots.txt text or a public robots.txt URL plus an optional path. Includes merged matching groups, octet-normalized longest-match decisions, per-crawler evidence, transport status, crawler-registry provenance and policy snippets.Answers a question. Declared read only.
pagehttps://admintoolkit.io/
implementation
viaimperative
entry pointdocument
registered after157ms
executepresent
api surface
contentoptional
crawlersoptional
pathoptional
urloptional
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contenttrue
titlenot declared
2 findings
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 19 names are over Chrome's 30-character guidance; 24 names do not start with a verb (admintoolkit_check_ai_crawler_access).
fix
{ name: "admintoolkit_check_ai_crawler_access" /* short, unique, verb-based */ }
warningHuman parity
0 / 8
24 of 24 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.
admintoolkit_check_ai_crawler_access, admintoolkit_validate_llms_txt, admintoolkit_validate_a2a_agent_card, admintoolkit_validate_webmcp_tool, admintoolkit_check_mx_records
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="admintoolkit_check_ai_crawler_access" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "admintoolkit_check_ai_crawler_access",
  "description": "Return a read-only RFC 9309 robots.txt access report for AI and search crawlers. Accepts robots.txt text or a public robots.txt URL plus an optional path. Includes merged matching groups, octet-normalized longest-match decisions, per-crawler evidence, transport status, crawler-registry provenance and policy snippets.",
  "inputSchema": {
    "additionalProperties": false,
    "anyOf": [
      {
        "required": [
          "url"
        ]
      },
      {
        "required": [
          "content"
        ]
      }
    ],
    "properties": {
      "content": {
        "description": "Pasted robots.txt content to validate locally, e.g. 'User-agent: GPTBot'.",
        "type": "string"
      },
      "crawlers": {
        "description": "Crawler tokens to evaluate as an array, e.g. ['GPTBot','Google-Extended'].",
        "items": {
          "type": "string"
        },
        "type": "array"
      },
      "path": {
        "description": "Path to evaluate against robots.txt rules, e.g. '/' or '/tools/'.",
        "type": "string"
      },
      "url": {
        "description": "Robots.txt URL or bare domain to fetch, e.g. 'https://example.com/robots.txt'.",
        "format": "uri",
        "type": "string"
      }
    },
    "required": [],
    "type": "object"
  },
  "annotations": {
    "readOnlyHint": true,
    "untrustedContentHint": true
  }
}
Showing admintoolkit_check_ai_crawler_access

Findings

WebMCP use

81 / 100 · weight 50
passTools registered
4 / 4
24 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. The page does carry an origin-trial token, but it does not grant WebMCP on this origin.
passRegistration timing
4 / 4
Every measured tool registered within 158.09999990463257ms of navigation.
tooladmintoolkit_check_tls_configuration
passCanonical entry point
4 / 4
All 24 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 24 tools declare a structurally valid object input schema.
passSchema quality
4 / 4
All 24 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 24 tools declare an execute handler.
passAnnotations present
4 / 4
All 24 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 (24 declared hints checked).
passUntrusted content hint
2 / 2
All 1 tool that looks like it returns third-party text declares untrustedContentHint.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
24 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

30 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 19 names are over Chrome's 30-character guidance; 24 names do not start with a verb (admintoolkit_check_ai_crawler_access).
tooladmintoolkit_check_ai_crawler_access
fix
{ name: "admintoolkit_check_ai_crawler_access" /* 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.
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

0 / 100 · weight 20
warningHuman parity
0 / 8
24 of 24 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.
tooladmintoolkit_check_ai_crawler_access
admintoolkit_check_ai_crawler_access, admintoolkit_validate_llms_txt, admintoolkit_validate_a2a_agent_card, admintoolkit_validate_webmcp_tool, admintoolkit_check_mx_records
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="admintoolkit_check_ai_crawler_access" 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
24
run time
3s
finished
Aug 28, 2026