Skip to main content
Glama

LinkVet

Check robots.txt rules for a URL (incl. AI bots)

check_robots
Read-onlyIdempotent

Is a given user agent allowed to fetch this URL under the site's robots.txt (RFC 9309 longest-match rules)? Returns allowed, matched_rule, crawl_delay, declared sitemaps, a per-bot verdict for 20 AI/search crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot...), and whether the site publishes /llms.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": "check_robots"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
user_agentNoUser agent token to evaluate (default *)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the description only needs to add context, and it does: it discloses the RFC rule semantics, the default '*' agent, and the fact that each call returns a 20-bot verdict list plus llms.txt status. It omits error behavior for unreachable robots.txt, which keeps it out of 5 territory.

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 request is front-loaded as a question and the rest is a compact enumeration of returned fields. The output list is dense with parenthetical examples, but each item carries information an agent needs, so there is no real waste.

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?

With no output schema, the description correctly carries the burden of describing returns (allowed, matched_rule, crawl_delay, sitemaps, per-bot verdicts, llms.txt). For a two-parameter read-only tool with no nested objects, this is nearly complete, with the bare url parameter the only real omission.

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 sits at 50%: the url parameter has no description at all, and user_agent already says '(default *)'. The description adds a little meaning by framing user_agent as the token evaluated under longest-match rules, but it does not explain the url parameter or accepted agent formats, so the gap is only partly filled.

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

Purpose5/5

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

The description opens with a specific verb+resource question ('Is a given user agent allowed to fetch this URL under the site's robots.txt') and names the standard (RFC 9309 longest-match). That is clearly distinct from siblings like check_url or read_page, which do not evaluate robots rules.

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 question form: an agent should call this to test crawl permission before fetching. But it never states when to prefer it over check_url or read_page, and it offers no exclusions or prerequisites (e.g. what to do if robots.txt is missing or unreachable).

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