Skip to main content
Glama

Format JSON

bursia_json_format
Read-onlyIdempotent

Pretty-print JSON with 2-space indentation, or minify it to one line. Returns the formatted JSON text. Pure computation, 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": {
      "json": "<json>"
    },
    "name": "bursia_json_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesThe JSON text to format.
modeNopretty (default, 2-space indent) or minify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / json / description
      Added value: +"The JSON text to format."
    • addedInput schema / properties / mode / description
      Added value: +"pretty (default, 2-space indent) or minify."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "pretty",
      +  "minify"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: 'Returns the formatted JSON text' discloses the return shape (no output schema exists) and 'Pure computation, free' tells the agent there is no cost or external call.

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 short sentences, zero waste. The capability and both modes come first, with the return value and cost note trailing as supporting detail.

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 two-parameter pure transformation, the description covers what it does, both modes, the return value (compensating for the missing output schema), and cost. Combined with rich annotations, nothing an agent needs to invoke it correctly is absent.

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% and the mode parameter has an enum with documented values, so the schema already carries the semantics. The description confirms the 'pretty = 2-space' default but adds no syntax, error-handling, or edge-case detail 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?

States a specific verb (pretty-print / minify) on a specific resource (JSON) and names both modes with their exact effect (2-space indent, one line). This is inherently distinguishable from JSON siblings like bursia_json_validate, bursia_json_diff, and bursia_json_path, which transform or inspect rather than reformat.

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?

The 'or minify it to one line' phrasing implies which mode to pick, but there is no explicit when-to-use guidance, no mention of the validate/diff siblings as alternatives, and no stated precondition (e.g., that input must be valid JSON). Usage is inferable rather than stated.

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