Skip to main content
Glama

net-web-media

robots_txt_evaluate

Parse robots.txt groups, Sitemaps, and Disallow/Allow path precedence to test whether a specific User-Agent is allowed to crawl a target URL path.

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

Input Schema

NameRequiredDescriptionDefault
textNorobots.txt content.
testPathNo/
userAgentNo*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that evaluation covers groups, Sitemaps, and Disallow/Allow precedence, which is real algorithmic context. However, it says nothing about the result shape (allow/deny verdict, matched rule, discovered sitemaps) or how malformed or empty robots.txt content is handled.

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?

A single dense sentence with the parsing scope front-loaded and the outcome clause last. No filler, no repetition of the tool name.

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?

Given no output schema and no annotations, the description covers what the tool does and the precedence logic it applies, which is the core need. The main gaps are the result contents and input format expectations, which leaves it slightly short of complete for a zero-annotation tool.

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 is only 33% — just 'text' is documented, while 'testPath' and 'userAgent' carry defaults but no descriptions. The description partially compensates by conceptually mapping those parameters ('target URL path', 'specific User-Agent'), but it does not state expected formats (path vs full URL, UA token vs full string) or the wildcard default behavior.

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 ('Parse ... to test') against a specific resource ('robots.txt groups, Sitemaps, and Disallow/Allow path precedence') and names the decision it produces ('whether a specific User-Agent is allowed to crawl a target URL path'). An agent can distinguish this from nearby siblings such as sitemap_xml_validate, though the description does not explicitly contrast them.

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 clearly: feed robots.txt content plus a path and user agent to get a crawl verdict. There is no explicit when-not-to-use statement, no mention of alternatives (e.g. sitemap validation), and no note about prerequisites such as needing fetched robots.txt text.

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