Skip to main content
Glama
Crawl Readiness MCP Server

Crawl Readiness MCP Server

Check AI Readiness

check_ai_readiness
Read-only

Check whether AI crawlers like ChatGPT, Claude, and Perplexity can access a site; return a 0–100 readiness score, per-crawler access status, and prioritized fixes.

Instructions

Check whether AI crawlers (ChatGPT, Claude, Perplexity, Google AI, and 50+ others) can access a website, and what access policy it states. Returns a 0-100 AI readiness score, per-crawler access status, detected AI-specific files (llms.txt, agents.json), structured data presence, meta signals, and a prioritized fix list. The score counts the crawlers that feed AI search and answers: each entry in robots.results carries its purpose and whether it is scored, and training-only crawlers are listed but never counted, so blocking them does not lower the score. Fixes marked extra: true (llms.txt, agents.json, Content-Signal, a markdown copy, agent-ready forms) are informational 'Going further' items and do not affect the score; present them as optional. Use this as the first step whenever a user asks whether AI can read a site.

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_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website URL to check (e.g. 'example.com' or 'https://example.com/page').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it explains scoring rules (training-only crawlers listed but never counted, blocking them doesn't lower the score) and how to present `extra: true` fixes as optional. That is exactly the interpretive context an agent needs to avoid misreporting results.

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

Conciseness4/5

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

Front-loaded with purpose and output, then the scoring caveats. It's dense but each clause carries real information; the single sentence about `robots.results` is heavy but load-bearing.

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?

No output schema exists, and the description compensates by enumerating the return payload (score, per-crawler status, AI files, structured data, meta signals, prioritized fixes). An agent can call it and interpret the result without further documentation.

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?

Only one parameter, and the schema already documents it fully (100% coverage, with examples for both bare domain and full URL forms). The description adds no syntax or format guidance beyond the schema, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Check whether AI crawlers can access a website') and immediately scopes it with the crawler set and the policy question. It is clearly distinct from sibling generation/validation tools like validate_robots or generate_llms_txt.

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?

Explicitly routes the agent: 'Use this as the first step whenever a user asks whether AI can read a site.' That's a clear triggering condition, though it doesn't name when-not to use it or point to an alternative tool.

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