Skip to main content
Glama

Fix a robots.txt

fix_robots
Read-onlyIdempotent

The domain's served robots.txt, corrected: * group rules copied into named groups that lacked them (shadowing), a Sitemap line added when missing, a minimal replacement when the served file was HTML. Every change is listed at the top; nothing else is touched.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower, and the description still adds real context: the three specific categories of edit, that changes are reported at the top, and that nothing outside those edits is touched. The one residual ambiguity is whether the corrected file is written back to the server or only returned, since 'corrected' plus a 'fix' title could read as a mutation to some agents.

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 dense sentence with a front-loaded subject ('The domain's served robots.txt, corrected') and a colon-delimited fix list; there is essentially no filler. It is slightly packed, but every clause carries information an agent needs.

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 one-parameter tool with no output schema and full annotation coverage, the description supplies what matters: the scope of edits, the reporting of changes at the top, and the guarantee that nothing else is modified. It stops short of describing the return shape precisely or routing the agent against sibling tools, which is a minor but real gap.

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 0% for the single required 'domain' parameter, so the description must carry it. It clarifies that the domain identifies a live served robots.txt (implying a network fetch rather than a local path), but gives no format guidance such as bare hostname versus URL.

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?

The description names a concrete resource and operation (the domain's served robots.txt, corrected) and enumerates the exact transformations applied: group rules copied into named groups to fix shadowing, a Sitemap line added when missing, and a minimal replacement when the served file is HTML. That is specific enough to separate it from a plain fetch tool like resolve_robots, though no sibling is named 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?

Use conditions are implied by the fix list (shadowed groups, missing Sitemap, HTML served instead of text), which lets an agent infer when this tool is relevant. However, there is no explicit statement of when to prefer it over resolve_robots or check_site_safety, and no prerequisites such as needing the domain resolved first.

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.