mcp-v2-minimal

Overview Schema Source Related Servers Discussions Admin

Format JSON

json_format

Read-onlyIdempotent

Parse and pretty-print JSON text with a stable key order. Returns a readable error instead of throwing when input is invalid JSON, so formatting failures stay diagnosable.

Instructions

Parse JSON and return it pretty-printed with a stable key order. Returns a readable error instead of throwing when the input is not valid 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": {
      "json": "<json>"
    },
    "name": "json_format"
  }
}

Input Schema

Name	Required	Description	Default
`json`	Yes	The JSON text to format
`indent`	No	Spaces of indentation

Output Schema

Name	Required	Description	Default
`keys`	Yes
`formatted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real behavioral value beyond them: deterministic key ordering and, importantly, that invalid input yields a readable error rather than a thrown exception, which changes how an agent should handle failures.

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, each earning its place: the first states the transformation and the ordering guarantee, the second states the error-handling contract. Nothing is redundant or buried.

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?

An output schema exists, so return values need not be explained, and the description covers the two non-obvious behaviors an agent needs (stable ordering and non-throwing errors). Only minor edge cases, such as handling of very large inputs, are unaddressed, which is acceptable for a low-complexity utility.

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%, with both 'json' and 'indent' documented including default, min, and max, so the schema carries the parameter burden. The description adds no syntax, encoding, or formatting nuance beyond what the schema already states, making the baseline 3 correct.

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 ('Parse JSON and return it pretty-printed') and adds a scope detail ('stable key order') that distinguishes this from a generic JSON transform. An agent can immediately tell this is a formatting utility rather than a parser/validator or the sibling echo tool.

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 only implied: an agent infers it should call this when it wants readable JSON output. There is no explicit statement of when to use it versus alternatives, and no prerequisites or exclusions are given, though the single-sibling context makes this a low-stakes gap.

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

Deploy Server

Other Tools

echoA
json_formatA