Skip to main content
Glama
geo-seo-readiness-lite

geo-seo-readiness-lite

check_ai_crawler_access

Read-only

Checks robots.txt rules to see if AI search and training crawlers (OpenAI, Perplexity, Claude, Google, Bing) can access a given page path, revealing blocking directives that stop AI citation.

Instructions

Evaluate robots.txt for AI search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot), AI training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot) and Googlebot/Bingbot, for the given page path.

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

NameRequiredDescriptionDefault
urlYesPublic page or site URL, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered. The description adds useful scoping detail by naming which crawler classes are evaluated, but says nothing about fetching time, failure modes for unreachable sites, or what form the verdict takes.

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?

A single sentence, front-loaded with the verb and resource, with the crawler-list parenthetical earning its length by defining scope. No filler or redundant restatement of the name.

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

Completeness4/5

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

For a one-parameter read-only tool with no output schema, the description covers the essential question (which crawlers are checked against which robots.txt path). The only gap is that a reader cannot anticipate the shape of the result, which is a minor omission given a single trivial parameter.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but 'for the given page path' adds real meaning: it clarifies the URL is evaluated path-specifically rather than as a bare domain, which matters because robots.txt rules can be path-scoped. That nuance is not stated in the schema's 'Public page or site URL' text.

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?

Specific verb ('Evaluate') plus specific resource ('robots.txt') and an explicit enumeration of the crawler families covered (OAI-SearchBot, GPTBot, Google-Extended, Googlebot/Bingbot). The robots.txt focus alone is enough to separate it from siblings like check_llms_txt and check_sitemap without opening either schema.

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

Usage Guidelines3/5

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

The purpose implies when it applies (you want to know whether AI crawlers are allowed at a given path), but there is no explicit when-to-use/when-not guidance and no named alternative such as check_llms_txt or quick_readiness_report. An agent must infer routing from the resource name.

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