Skip to main content
Glama

Check robots.txt for agents

bursia_check_robots
Read-onlyIdempotent

Check one agent-readiness item on a public website: robots.txt para agentes (/robots.txt). Read-only, free.

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

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only, free' largely restates structured data. The genuinely additive parts are the 'public website' restriction and the exact endpoint fetched, but nothing is said about failure modes (unreachable domain, missing robots.txt) or what the result contains.

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?

One short sentence with the resource and scope front-loaded and no filler. The redundant bilingual 'para agentes' phrasing costs a little precision but not length.

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?

With a single fully-documented parameter and read-only annotations, most burden is covered, and no output schema exists so return shape is unexplained. An agent still doesn't know whether the check reports raw robots.txt content, a parsed verdict, or error states for missing files.

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 100% and the single parameter already documents 'Domain or https URL'; the description adds no format, normalization, or validation guidance beyond that. Baseline 3 applies since the schema does the work.

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 ('Check') and resource ('robots.txt'), scoped to one agent-readiness item, which implicitly separates it from the aggregate bursia_agent_readiness and from sibling checks like check_llms_txt or check_sitemap. The parenthetical path clarifies exactly what is fetched, though the mixed-language phrase 'robots.txt para agentes' is slightly noisy.

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?

'Check one agent-readiness item' implies this is the single-item variant versus the aggregate readiness tool, but no alternative is named and there are no explicit when/when-not conditions. 'Public website' is the only stated constraint.

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