Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

check_ai_bot_access

Check whether major AI search engines can access a website by inspecting its live robots.txt, helping you audit AI crawler permissions and avoid blocked citations.

Instructions

Check if major AI search engines (Claude, ChatGPT Search, Gemini, Google AI Overviews) are permitted or blocked by a website's live 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": {
      "domain": "<domain>"
    },
    "name": "check_ai_bot_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to inspect (e.g. 'stripe.com' or 'example.com')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real context by stating the source is the site's *live* robots.txt and by enumerating exactly which four crawler families are evaluated, which scopes the result set. However, it says nothing about return shape per bot, behavior when robots.txt is absent, network failure handling, or caching.

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?

One tight sentence, front-loaded with the action and immediately followed by the scope and data source. Every clause earns its place with no redundancy.

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

Completeness3/5

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

With no annotations and no output schema, the description is the only place an agent can learn what it gets back. It identifies the source and the crawler set, but leaves the response structure (per-bot allow/block verdicts?) and missing-robots.txt behavior undefined — a moderate but noticeable gap for a tool whose whole value is the returned verdicts.

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?

There is a single required parameter with 100% schema description coverage, including an example format, so the schema already does the work. The description adds nothing about accepted domain forms (subdomains, paths, protocols), so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb plus resource — checking whether named AI crawlers (Claude, ChatGPT Search, Gemini, Google AI Overviews) are allowed or blocked by a site's live robots.txt. An agent can immediately tell this is a read-only robots.txt inspection, though it never names or contrasts with a sibling such as generate_robots_txt or geo_audit_domain.

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?

Usage is only implied: an agent can infer this is the tool for 'is my site blocking AI crawlers right now.' There is no explicit when-to-use, no exclusion of alternatives (e.g., generating a robots.txt vs. checking the live one), and no stated prerequisites.

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