Httpbin

Robots Txt

robots_txt

Read-onlyIdempotent

Fetch a sample robots.txt from httpbin.org (/robots.txt). Use to test robots.txt parsing or as a content-type placeholder.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Sample robots.txt content
`status`	Yes	HTTP status code
`content_type`	Yes	Content-Type header

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "description": "Sample robots.txt content",
+      "type": "string"
+    },
+    "content_type": {
+      "description": "Content-Type header",
+      "type": "string"
+    },
+    "status": {
+      "description": "HTTP status code",
+      "type": "number"
+    }
+  },
+  "required": [
+    "status",
+    "content_type",
+    "body"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is fully declared. The description adds that it fetches from a specific URL, which is useful but minimal extra context beyond annotations.

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 two short sentences, no wasted words, and immediately conveys the tool's action and purpose.

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?

For a parameterless sample fetch tool with an output schema, the description provides sufficient information: the exact URL and two use cases. No further context is needed.

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?

There are no parameters, and the schema has 100% coverage (empty). Baseline is 4 for zero-parameter tools. The description does not need to add parameter details.

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 explicitly states it fetches a sample robots.txt from httpbin.org, and provides two specific use cases: testing robots.txt parsing or as a placeholder. This clearly distinguishes it from sibling tools like 'get' or 'post'.

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?

The description gives clear context on when to use this tool (testing parsing or placeholder), but does not mention when not to use or alternatives. However, the purpose is so specific that it is not ambiguous.

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

All Httpbin tools Inspect

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.