Skip to main content
Glama

BRAINIAC Technical SEO Audits

Test URLs against robots.txt

seo-technical_robots-txt-test
Read-onlyIdempotent

Evaluate path access for a user-agent against a caller-supplied robots.txt using RFC 9309 longest-match rules. Price $0.02 USDC. POST /api/v1/seo-technical/robots-txt-test. An unpaid call returns the x402 payment terms and does not run.

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": {
      "robotsTxt": "<robotsTxt>",
      "userAgent": "<userAgent>",
      "urls": "<urls>"
    },
    "name": "seo-technical_robots-txt-test"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesurls, array. Required.
robotsTxtYesrobotsTxt, string, length 0 to 512000. Required.
userAgentYesuserAgent, string, length 1 to 256. Required.

Output Schema

NameRequiredDescriptionDefault
groupNogroup. String.
resultsNoresults. Array.
sourcesNosources. Array.
sitemapsNositemaps. Array.
crawlDelayNocrawlDelay. Null.
limitationsNolimitations. Array.
unknownDirectivesNounknownDirectives. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the $0.02 USDC charge, the x402 payment flow where an unpaid call returns payment terms instead of results, and the RFC 9309 matching semantics. It does not describe output shape, but an output schema exists.

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?

Three tight sentences: purpose and semantics first, then cost, then endpoint. Nothing is repeated or padded, and the payment constraint, which materially affects invocation, is front-loaded ahead of the transport detail.

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 three-parameter read-only tool with full schema coverage and an output schema, the description covers purpose, matching semantics, and the payment precondition. Minor gaps remain around malformed-robots.txt handling and path-vs-URL input format, but nothing that would block a correct call.

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 the three parameters are already documented structurally. The description adds one useful clarification, that robotsTxt is supplied by the caller rather than retrieved, but says nothing about whether urls are absolute URLs or paths, which the wording 'path access' leaves slightly ambiguous. 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: evaluate path access for a user-agent against a caller-supplied robots.txt, with the matching standard (RFC 9309 longest-match) named. An agent can tell this validates robots.txt rules rather than, say, validating a sitemap or auditing canonicals, though it never names a sibling tool explicitly.

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 phrase 'caller-supplied robots.txt', which signals the tool does not fetch the file itself, and the payment note warns an unpaid call will not execute. There is no explicit when-to-use/when-not guidance or comparison to alternatives such as the sitemap or canonical audit tools.

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