Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

JSON formatter, pretty-print: pretty-print JSON with indentation, optionally with sorted keys

json_format
Read-only

Format JSON with indentation (2 or 4 spaces, or tabs) and optionally sorted keys. Returns the formatted text. Use to make machine JSON readable or to normalise it for diffs. Example: text={"b":2,"a":1}. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "text": "<text>"
    },
    "name": "json_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe JSON text
indentNo2 (default), 4 or tab
sortKeysNotrue to sort object keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: $0.01/call pricing, first 25 free, failed calls free, and that repeats are charged because calls are not idempotent. It also explicitly states it reads or computes only and changes nothing. The one omission is behavior on malformed JSON input.

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?

Front-loaded with purpose, options, and return value before billing detail. Sentences are mostly efficient, though the pricing/payment sentence is dense and could be split or trimmed.

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?

No output schema exists, so the description must describe the return, and it does ("Returns the formatted text"). For a simple 3-parameter transformation tool, the remaining gaps—invalid-input behavior and the loose parameter typing—are minor.

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%, so the baseline is 3; the description adds an example (text={"b":2,"a":1}) and confirms 2 is the default indent. It does not clarify the unusual string/number/boolean type union for indent and sortKeys, which could still confuse an agent.

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?

States a specific verb (format/pretty-print) and resource (JSON) plus the concrete options (2 or 4 spaces, tabs, sorted keys) and the return value. An agent can distinguish this from json_minify, json_validate, and json_repair by function alone.

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?

Gives explicit use contexts: to make machine JSON readable or to normalise it for diffs. That is clear when-to-use guidance. It does not explicitly name the opposite-goal alternative (minify) or the validation sibling, so it stops short of full when-not guidance.

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.