Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

ai_bot_robots_check

Check whether GPTBot, PerplexityBot, Google-Extended and other AI crawlers are allowed by 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": "ai_bot_robots_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL (path is evaluated against robots.txt)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it: it never says whether robots.txt is fetched live or cached, whether fetch failures/timeouts are reported, or what per-bot results come back. It adds the useful behavioral scope of which crawler families are covered, but that is the only disclosure beyond the obvious.

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?

One front-loaded sentence with no filler and no repetition. It is efficient, though the brevity is also the source of the missing behavioral detail.

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

Completeness2/5

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

There is no output schema and no annotations, so the description is the only place an agent could learn the shape of the answer (e.g. allowed/blocked per named bot, or crawler list coverage). It stops at the question the tool answers and says nothing about the response, leaving the agent guessing what to expect back.

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 coverage is 100% and the schema itself explains that the path is evaluated against robots.txt, so the single parameter is already well documented. The description confirms the robots.txt evaluation context but adds no syntax, default, or path-handling detail beyond the schema.

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?

States a specific verb and resource: checking whether named AI crawlers (GPTBot, PerplexityBot, Google-Extended) are allowed by robots.txt. That is concrete enough to separate it from robots/llms.txt-oriented siblings, though it never explicitly contrasts itself with llms_txt_auditor or technical_seo_composite.

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 by the topic: an agent can infer it is for AI-crawler access questions, but there is no statement of when to prefer it, no prerequisites (e.g. site must be publicly reachable), and no named alternative for broader robots.txt auditing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources