xfix

Check AI crawler access

check_ai_crawler_access

Read-only

Reads a site's robots.txt the way 9 crawlers do (Googlebot, Bingbot, Applebot, OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User) and returns which may fetch the given page and the rule that blocks each one. Does not see CDN or firewall rules. Use when the user asks which bots or crawlers can access, crawl or read a site, or asks about robots.txt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_ai_crawler_access"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The full address of one public page, for example https://example.com/page.

Output Schema

Name	Required	Description	Default
`url`	Yes
`tool`	Yes
`cached`	Yes
`limits`	Yes
`status`	Yes
`verdict`	Yes
`findings`	Yes
`checked_at`	Yes
`report_url`	Yes
`crawler_access`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the precise crawler roster evaluated, that it returns the specific blocking rule per bot, and an explicit blind spot ('Does not see CDN or firewall rules'). It does not mention whether robots.txt is fetched live, caching, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first front-loads the operation, its inputs, and its output; the second carries the limitation and the usage trigger. No filler, no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value detail is not the description's burden, and it still briefly signals the return shape. Combined with the enumerations and the CDN/firewall blind spot, an agent has everything needed to call it correctly and to set expectations about result coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and there is a single required url parameter, so the baseline is 3. The description adds no syntax, format, or constraint detail beyond what the schema already states ('full address of one public page').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Reads a site's robots.txt') plus the exact scope: nine named crawlers, returning which may fetch the page and the blocking rule. An agent can distinguish this from siblings like check_page_readability or check_store_ai_readiness purely from the name and this sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: 'Use when the user asks which bots or crawlers can access, crawl or read a site, or asks about robots.txt.' That is a clear, actionable condition. It does not name an alternative tool or an exclusion case, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All xfix tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?