Skip to main content
Glama

AEO Auditor — AI Search & Agent Readiness Engine

validate_robots_txt

Validate a robots.txt file or live domain robots.txt against 10 AI search crawlers (GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended) and generate a 100/100 compliant configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_robots_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoOptional domain to fetch live /robots.txt from (e.g. "example.com").
robotsTxtContentNoOptional raw robots.txt content string to validate directly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose that the tool both validates and generates a compliant configuration — an output behavior beyond a pure check. However, it does not say what the validation results look like, whether the domain path performs a live network fetch (and what happens on fetch failure), or whether anything is written anywhere.

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?

A single front-loaded sentence with the resource and crawler scope first, no filler. It loses a point for the internal inconsistency in the crawler count, which slightly muddies an otherwise tight statement.

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?

Given two optional parameters and no output schema, the description should describe the shape of the result — per-crawler pass/fail, the generated configuration, or remediation hints. It gestures at both outputs but leaves the return contract, error behavior for unreachable domains, and whether the parameters are mutually exclusive unspecified.

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 description coverage is 100%, so both parameters (domain and robotsTxtContent) are already documented with examples in the schema. The description only restates the file-or-live-domain duality at a high level and adds no format, precedence, or mutual-exclusivity detail beyond the schema. 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?

States a specific verb and resource: validates a robots.txt file or a live domain's robots.txt against named AI crawlers and produces a compliant configuration. The scope is concrete enough to separate it from audit_domain or get_domain_benchmark. Minor deduction for the inconsistency of claiming '10 AI search crawlers' while listing only seven, and for not naming which sibling it replaces.

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 two input modes (raw content vs. live domain) imply when each applies, but the description never says when to choose this over audit_domain, generate_remediation_kit, or get_domain_benchmark. No prerequisites or exclusions are stated, so the agent must infer routing from the sibling names alone.

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