OnlineCyberTools MCP (280+ filterable tools)

security_robots_txt_generator

Read-onlyIdempotent

Generate RFC 9309-compliant robots.txt files from structured rule groups. Parse existing files or choose from preset rule sets.

Instructions

Robots.txt Generator (Build, Parse, and Preset RFC 9309 Crawler Rules). Assemble, parse, or template an RFC 9309 robots.txt file from structured user-agent groups. The 'operation' field selects the mode: 'generate' serializes "input" (groups of user-agents with allow/disallow paths, optional crawl-delay, sitemaps, host, comment) into robots.txt text plus validation warnings; 'parse' round-trips an existing robots.txt string back into the same structured shape; 'presets' returns 12 ready-made rule sets (allow-all, block-all, WordPress, Drupal, Joomla, Magento, Shopify, Ghost, Next.js, block-AI-scrapers, custom); 'commonUserAgents' returns a 50-entry crawler reference table. Generation only assembles and validates strings — it does NOT fetch, test, or deploy the file, and crawler compliance is voluntary. Use seo_sitemap_generator to build the sitemap this file points at, or security_htaccess_generator for Apache server-config directives rather than crawler access rules. Pure local computation: read-only, non-de

Input Schema

TableJSON Schema

Name	Required	Description
`operation`	Yes	Mode to run. 'generate' needs "input"; 'parse' needs "text"; 'presets' and 'commonUserAgents' take no other fields.
`input`	No	Robots.txt definition for operation "generate". Requires a non-empty "groups" array.
`text`	No	Existing robots.txt text to parse for operation "parse".

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when the operation succeeded.
`operation`	No	Echo of the operation performed.
`result`	No	Payload for the chosen operation. For "generate": robotsTxt/warnings/lineCount. For "parse": groups/sitemaps/host/comment. For "presets" and "commonUserAgents" this is instead a JSON array.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / input / additionalProperties
```
Added value: +false
```

addedInput schema / properties / input / description

Added value: +"Robots.txt definition for operation \"generate\". Requires a non-empty \"groups\" array."

addedInput schema / properties / input / properties / comment

Added value: +{
+  "description": "Optional comment block prepended as '#' lines.",
+  "type": "string"
+}

addedInput schema / properties / input / properties / groups / description

Added value: +"Rule groups; each must be an object. A group with no user-agents defaults to '*'."

addedInput schema / properties / input / properties / groups / items / properties / allow / description

Added value: +"Allow paths starting with '/' or '*'; a missing leading slash is auto-prefixed and warned."

addedInput schema / properties / input / properties / groups / items / properties / crawlDelay

Added value: +{
+  "description": "Optional non-negative crawl-delay seconds; emitted with a portability warning (Google ignores it).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / input / properties / groups / items / properties / disallow / description
```
Added value: +"Disallow paths; an empty string means \"allow everything\" per RFC 9309."
```
addedInput schema / properties / input / properties / groups / items / properties / userAgents / description
```
Added value: +"User-agent tokens for the group (e.g. Googlebot, '*'); empty defaults to '*'."
```
removedInput schema / properties / input / properties / groups / items / required
```
Removed value: -[
-  "userAgents",
-  "allow",
-  "disallow"
-]
```
addedInput schema / properties / input / properties / groups / minItems
```
Added value: +1
```

addedInput schema / properties / input / properties / host

Added value: +{
+  "description": "Optional non-standard Host directive (legacy Yandex).",
+  "type": "string"
+}

addedInput schema / properties / input / properties / sitemaps / description

Added value: +"Optional absolute sitemap URLs; non-absolute values are kept but warned."

changedInput schema / properties / input / required

Previous value: -[
-  "groups",
-  "sitemaps"
-]New value: +[
+  "groups"
+]

addedInput schema / properties / operation / description

Added value: +"Mode to run. 'generate' needs \"input\"; 'parse' needs \"text\"; 'presets' and 'commonUserAgents' take no other fields."

addedInput schema / properties / operation / enum

Added value: +[
+  "generate",
+  "parse",
+  "presets",
+  "commonUserAgents"
+]

addedInput schema / properties / text

Added value: +{
+  "description": "Existing robots.txt text to parse for operation \"parse\".",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "operation",
-  "input"
-]New value: +[
+  "operation"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "operation": {
+      "description": "Echo of the operation performed.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Payload for the chosen operation. For \"generate\": robotsTxt/warnings/lineCount. For \"parse\": groups/sitemaps/host/comment. For \"presets\" and \"commonUserAgents\" this is instead a JSON array.",
+      "properties": {
+        "comment": {
+          "description": "\"parse\": leading comment block if present.",
+          "type": "string"
+        },
+        "groups": {
+          "description": "\"parse\": reconstructed rule groups.",
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "host": {
+          "description": "\"parse\": Host directive value if present.",
+          "type": "string"
+        },
+        "lineCount": {
+          "description": "\"generate\": number of emitted lines.",
+          "type": "integer"
+        },
+        "robotsTxt": {
+          "description": "\"generate\": the serialized robots.txt text.",
+          "type": "string"
+        },
+        "sitemaps": {
+          "description": "\"parse\": absolute sitemap URLs found.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "warnings": {
+          "description": "\"generate\": severity-tagged validation notes; empty when clean.",
+          "items": {
+            "properties": {
+              "location": {
+                "description": "Where the warning applies (group/sitemaps/overall).",
+                "type": "string"
+              },
+              "message": {
+                "description": "Human-readable warning text.",
+                "type": "string"
+              },
+              "severity": {
+                "description": "Warning severity.",
+                "enum": [
+                  "info",
+                  "low",
+                  "medium",
+                  "high"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the operation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that generation only assembles and validates strings, does not fetch/test/deploy, and that crawler compliance is voluntary. No contradiction.

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?

The description is front-loaded with a clear summary and uses bullet-like structure for modes. Slightly lengthy but every sentence is useful. Minor truncation ('non-de') but does not detract.

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

Completeness5/5

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

Given the complexity (multiple modes, nested input, output schema), the description covers operation modes, input requirements, limitations, and alternative tools. Adequate for an agent to select and invole the tool correctly.

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 coverage is 100% with good descriptions. The tool description adds context beyond the schema, such as explaining each operation mode in detail and listing the preset names. This adds value, earning above baseline.

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 title and description clearly state the tool builds, parses, and presets robots.txt files per RFC 9309. It distinguishes from sibling tools by mentioning security_htaccess_generator and seo_sitemap_generator as alternatives for different purposes.

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

Usage Guidelines5/5

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

Explicit guidance on when to use each operation mode, and exclusions: use seo_sitemap_generator for sitemaps, security_htaccess_generator for Apache directives. Also states limitations: does not fetch, test, or deploy the file.

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

Deploy Server