Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

robots.txt generator

robots_txt_generator

Build a robots.txt: allow or block all, custom disallow paths, AI-crawler blocking, crawl-delay and sitemap. Runs on smart-tools.xyz.

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

Input Schema

NameRequiredDescriptionDefault
accessNoallow all, block all, or custom (default allow)
localeNoLanguage for the source_url link (default en)
sitemapNoSitemap URL (optional)
block_aiNoAlso block common AI crawlers (default false)
disallowNoPaths to disallow (used when access=custom)
crawl_delayNoCrawl-delay in seconds (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention output format, whether it modifies any hosted files, or any side effects. The 'Runs on smart-tools.xyz' line adds little context. More transparency is needed about what the tool actually returns or does.

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 concise and front-loaded with the key purpose. Two short sentences convey all main features without waste. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should explain what the tool returns, but it does not. It also fails to clarify parameter dependencies (e.g., disallow only used when access=custom). Despite covering features, important context about output and parameter interactions is missing.

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 100% (baseline 3). The description mentions most parameters (access, disallow, block_ai, crawl_delay, sitemap) but omits locale and adds no new meaning beyond the schema. It maps features to parameters but without extra detail.

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 builds a robots.txt file with specific capabilities (allow/block all, custom disallow paths, AI crawler blocking, crawl-delay, sitemap). It is distinct from sibling generator tools like htaccess_generator and gitignore_generator.

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 usage context through its purpose but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or alternative references are provided.

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

All SmartTools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources