Skip to main content
Glama
Sign In

Citehound

by io.github.andacuzel
OverviewDiscussionsAdmin

Generate an AI-crawler robots.txt

generate_robots_txt
Read-onlyIdempotent

Builds a robots.txt file that explicitly allows or blocks named AI crawlers from Citehound’s tracked list of 10, plus an optional Sitemap line. Pure text generation — fetches nothing. Call list_ai_crawlers first if you need the exact tracked crawler names.

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

Input Schema

NameRequiredDescriptionDefault
allowNoCrawler names to explicitly allow, e.g. ["GPTBot", "ClaudeBot"]. Must be names from the tracked list.
blockNoCrawler names to explicitly block. Must be names from the tracked list, and must not overlap with "allow".
sitemap_urlNoOptional absolute sitemap URL to add as a Sitemap: line, e.g. "https://example.com/sitemap.xml".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

"Pure text generation — fetches nothing" is exactly the behavioral distinction an agent needs versus scan_site, and it reinforces the openWorldHint=false / readOnlyHint=true profile with site-specific framing. It also bounds the domain by stating the tracked list has 10 entries.

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?

Three tight sentences: what it builds, what it does not do, and what to call first. Front-loaded with the outcome and zero filler.

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?

Covers purpose, non-network behavior, and the prerequisite lookup for a zero-required-parameter tool with no output schema. It does not say what the return looks like (raw text vs. structured result) or what happens on allow/block overlap, leaving small gaps.

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%, so all three parameters (allow, block, sitemap_url) are already documented with examples and the allow/block non-overlap rule. The description adds only the "tracked list of 10" quantification and the "optional Sitemap line" note, which the schema already conveys.

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?

Specific verb+resource (builds a robots.txt file) with the exact scope stated: allow/block named AI crawlers from a fixed tracked list of 10, plus an optional Sitemap line. It is clearly distinguishable from generate_llms_txt and scan_site without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the sibling list_ai_crawlers when exact crawler names are needed, giving a concrete prerequisite. It stops short of stating when-not to use this tool (e.g., use scan_site to actually inspect a site), so it falls short of a full 5.

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

All Citehound toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources