Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_ai_bot_robots_check

Checks whether AI crawlers like GPTBot, PerplexityBot and Google-Extended are allowed by a site's robots.txt, so you can verify SEO and generative engine readiness.

Instructions

[SEO & GEO Readiness] Check whether GPTBot, PerplexityBot, Google-Extended and other AI crawlers are allowed by robots.txt Measured p50 13 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://seo.caelaralabs.com.

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": "caelara_seo_ai_bot_robots_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL (path is evaluated against robots.txt)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. It discloses latency benchmarks and the backing endpoint host, which is useful, but says nothing about what is returned (per-bot allow/deny verdicts? raw robots.txt?), whether the fetch happens live, or how failures/absent robots.txt are handled.

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?

The purpose is front-loaded in one compact clause and nothing is padded with marketing prose. The benchmark and endpoint sentences are secondary but short, and the missing terminal punctuation makes the first sentence run on slightly.

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?

For a simple single-parameter read tool this covers the core intent, but with no output schema the description should describe the shape of the verdict (which crawlers are allowed/blocked). That omission leaves the agent guessing about the response.

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?

With one parameter and 100% schema description coverage, the schema already explains that the URL's path is evaluated against robots.txt. The description adds no extra meaning beyond that, so baseline 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 and resource ('Check whether ... AI crawlers are allowed by robots.txt') and names the concrete crawlers inspected (GPTBot, PerplexityBot, Google-Extended). It is clear what the tool does, though it never distinguishes itself from adjacent siblings such as the llms.txt auditor or the GEO readiness 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 implied by the '[SEO & GEO Readiness]' tag and the robots.txt framing, but there is no explicit statement of when to reach for this versus the composite or llms.txt tools, and no prerequisites are mentioned. An agent must infer the selection rule.

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

Deploy Server

Other Tools