Httpbin

Html Anything

html_anything

Read-onlyIdempotent

Fetch a sample HTML response from httpbin.org (/html). Use to verify HTML content-type handling or as a placeholder in tests.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Sample HTML response
`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 HTML response",
+      "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 convey read-only and idempotent behavior. The description adds that it fetches from httpbin.org (/html), confirming the resource. No further behavioral details (e.g., rate limits) are provided, but annotations cover safety.

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?

Two concise sentences with no filler. The key information is front-loaded.

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 tool with an output schema, the description fully covers what the tool does and why to use it. No gaps.

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, so schema coverage is 100%. The description adds no extra param info, which is acceptable. Baseline 4 applies for zero parameters.

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 action ('Fetch a sample HTML response from httpbin.org (/html)') and specifies its purpose ('verify HTML content-type handling or as a placeholder in tests'). It distinguishes from sibling tools like json_anything or xml_anything.

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 provides explicit use cases (verifying HTML handling, placeholder in tests) but does not mention when not to use it or alternatives. However, given the simplicity, this is clear enough.

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.