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

robotstxt-ai-mcp

by sharozdawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_bot_status

Check if a specific bot is blocked or allowed on a website by analyzing its robots.txt file.

Instructions

Check if a specific bot is blocked or allowed on a given website by fetching and analyzing its robots.txt.

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>",
      "bot_name": "<bot_name>"
    },
    "name": "check_bot_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website URL to check (e.g. https://example.com)
bot_nameYesThe bot user-agent string to check (e.g. 'GPTBot', 'ClaudeBot'). Use list_ai_bots to see available names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so description fully relies on text. It discloses the method (robots.txt analysis) but doesn't state non-destructive nature, rate limits, or error handling. Adequate but not comprehensive.

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?

Single, front-loaded sentence with no waste. Every word serves the purpose.

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?

No output schema, so description should hint at return values. It only says 'check if blocked or allowed' without describing the result format. Sibling tools exist but no guidance on selection.

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

Parameters4/5

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

Schema description coverage is 100%. Description adds context (e.g., 'website URL', 'bot user-agent string') and suggests using list_ai_bots, adding value beyond schema field descriptions.

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?

The description clearly states the tool checks bot status via robots.txt, with specific verb (check) and resource (bot on website). It distinguishes from siblings like list_ai_bots, which lists bot names.

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?

Implied usage from required parameters, but no explicit when-to-use vs alternatives or exclusion criteria. It hints at using list_ai_bots for bot names, but no direct comparison with analyze_robots or fetch_robots.

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