Skip to main content
Glama

robots_txt

Fetch and parse a domain's robots file to extract user-agent rules, allow/disallow paths, and sitemap URLs, flagging sensitive-looking directories for OSINT review.

Instructions

Fetch and parse robots.txt: user-agent groups, disallow/allow rules, sitemaps.

Flags sensitive-looking paths (admin, api, backup, private, .git, config).

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": {
      "domain": "<domain>"
    },
    "name": "robots_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose output shape (groups, rules, sitemaps) and an extra behavior not in the schema (flagging sensitive-looking paths like admin, api, .git), but it says nothing about error behavior when robots.txt is missing, redirects, or whether the fetch is live versus cached.

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?

Two short sentences, front-loaded with the fetch/parse purpose followed by the notable flagging behavior. No filler; the only minor weakness is the vague hedge 'sensitive-looking'.

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 one-parameter, no-output-schema tool, the description covers what is returned reasonably well, but leaves the domain argument's format and the missing-file case undocumented. Those gaps matter because there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, and the description does not compensate. It never states the expected domain format (bare host vs. full URL), so an agent gets no more meaning from the description than from the bare 'Domain' schema title.

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 (fetch and parse) and a specific resource (robots.txt), then enumerates the returned content (user-agent groups, disallow/allow rules, sitemaps). It is clearly distinct from siblings like security_txt or api_discovery, though it does not name them 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 only implied by the domain of the tool: an agent can infer this is for reading a site's crawl directives during recon. There is no explicit when-to-use, no mention of when to prefer security_txt or api_discovery, and no prerequisites stated.

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