devutils-mcp-server

json_format

Pretty-print a JSON string with configurable indentation, or minify it to reduce size.

Instructions

Format (pretty-print) a JSON string with configurable indentation. Can also minify JSON.

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

Input Schema

Name	Required	Description	Default
`input`	Yes	The JSON string to format
`indent`	No	Number of spaces for indentation (0 = minify, default: 2)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided; description adds behavior beyond schema (indent=0 means minify). However, does not disclose error handling (e.g., on invalid JSON), output format, or side effects.

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 sentences, zero fluff. Front-loaded with primary action, secondary capability in second sentence. Efficient and clear.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; description does not state return value (expected formatted JSON string). For simple tool, missing error/edge case info. Adequate but not complete.

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 has 100% coverage with clear descriptions. Description reinforces that indent controls spacing and minification, but adds minimal new info beyond schema.

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?

Clearly states the action (format/pretty-print/minify) and resource (JSON string), with configurable indentation. Distinguishes from sibling tools like json_validate and json_path_query.

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?

Implies usage for formatting or minifying JSON, but no explicit guidance on when to use vs siblings (e.g., validation, query). Lacks when-not or alternative tool references.

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