Skip to main content
Glama
Sign In
robotstxt-ai-mcp

robotstxt-ai-mcp

by sharozdawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

analyze_robots

Analyze robots.txt content to detect which AI crawlers are blocked or allowed. Provides a clear list of bot statuses.

Instructions

Analyze pasted robots.txt content. Returns which AI bots are blocked or allowed based on the rules.

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": {
      "content": "<content>"
    },
    "name": "analyze_robots"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe robots.txt content to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool returns which AI bots are blocked/allowed, but does not disclose error handling, input format validation, or any side effects. For a read-only analysis tool, this is minimally adequate.

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?

The description is extremely concise with two sentences. It front-loads the action and resource, and every sentence provides essential information. There is no wasted text.

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 the simplicity of the tool (one parameter, no output schema), the description covers what it does and what it returns. It could mention the output format or limitations, but for a low-complexity tool it is largely complete.

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 parameter description ('The robots.txt content to analyze') is clear. The description adds 'pasted' which slightly clarifies expected input but does not provide significant additional meaning beyond the schema.

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?

Description uses a specific verb ('Analyze') and resource ('pasted robots.txt content'). It clearly distinguishes from sibling tools like 'fetch_robots' (retrieves content) and 'generate_robots' (creates content), making its unique function evident.

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?

The description implies using this tool when you have robots.txt content to analyze, but it does not explicitly state when to use it versus alternatives like checking a specific bot status or fetching content first. No exclusions or alternative tool names are mentioned.

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

Deploy Server

Other Tools