Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Pretty-print JSON

format
Read-only

Pretty-print a JSON string with configurable indentation (0-8) and return the minified form too. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/format

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "json": "<json>"
    },
    "name": "format"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesJSON text to pretty-print
indentNoSpaces per indentation level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds important behavioral context beyond them: cost ($0.001 USDC per call), payment protocol (x402 v2 on Base), and the fact that minified output is also returned. It does not cover error behavior or rate limits, preventing a top score.

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 two sentences and front-loads the core operation before pricing and demo details. The pricing and demo information is relevant for an x402 agent, so it earns its place, though the sentence is slightly dense with unrelated facts.

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

Completeness4/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 explicitly notes that minified output is returned, which is important return-value context. Payment details and a demo URL are also included. It omits error handling or input validation behavior, but the definition is otherwise complete for a two-parameter formatting tool.

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%, so both parameters are already documented in the input schema. The description restates the indentation range (0-8) but adds no syntax, format, or edge-case meaning beyond what the schema provides.

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 uses a specific verb and resource ("Pretty-print a JSON string") and adds a second concrete outcome ("return the minified form too"). No sibling tool in the provided list does JSON formatting, so an agent can identify the unique operation immediately.

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?

Usage is strongly implied by the operation itself, and the description notes a free demo endpoint. However, it gives no explicit when-to-use/when-not guidance or mention of alternatives, leaving routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources