json_anythingFetch a sample JSON response from httpbin.org (/json). Use to verify JSON content-type handling or as a placeholder in tests.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Sample JSON response | |
| status | Yes | HTTP status code | |
| content_type | Yes | Content-Type header |
Changes observed during successful MCP inspections.
Output schema / properties / body / typePrevious value: -"object"New value: +[
+ "object",
+ "string"
+]Input schema / examplesAdded value: +[
+ {}
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "body": {
+ "description": "Sample JSON response",
+ "type": "object"
+ },
+ "content_type": {
+ "description": "Content-Type header",
+ "type": "string"
+ },
+ "status": {
+ "description": "HTTP status code",
+ "type": "number"
+ }
+ },
+ "required": [
+ "status",
+ "content_type",
+ "body"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so description needs only to add context. It adds that the response is from httpbin.org and is a placeholder, which is valuable but not essential 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no redundant language. Every word adds value: 'Fetch a sample JSON response' and the use cases are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given tool simplicity (no params, output schema present), description fully covers purpose and typical usage. No additional info needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has zero parameters, so schema description coverage is 100%. Description adds no parameter info but provides context about the returned data, which is helpful.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Fetch' and the specific resource 'sample JSON response from httpbin.org (/json)'. It distinguishes from siblings like xml_anything by focusing on JSON.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use: 'to verify JSON content-type handling or as a placeholder in tests'. Implies testing/validation context, though doesn't explicitly mention when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.