Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

format_json

Read-onlyIdempotent

Format, minify, validate, or analyze JSON documents. Cleans up syntax, sorts keys, and provides structure statistics.

Instructions

JSON Formatter, Minifier and Validator. Pretty-print, minify, validate, or analyze a JSON document, with optional indent width and alphabetical key sorting. Use format_json for plain text-in/text-out cleanup and syntax checking; use format_json_visualizer to browse JSON as an interactive tree, webdev_code_formatter for HTML/CSS/JS, or webdev_json_to_csv to convert JSON into CSV rows. Runs locally on the text you provide: read-only, non-destructive, parses nothing external, and is rate-limited (60 requests/minute for anonymous callers). Returns the processed output string, a validity flag, any parse error, structure analysis, and size and line statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoThe JSON document to process. Alias input is also accepted. Blank input returns isValid false with empty output.
inputNoAlias for json; used only when json is absent.
operationNoAction to perform. format pretty-prints, minify strips whitespace, validate only checks syntax (empty output), analyze returns structure statistics.format
indentNoIndentation for format: a space count as a string (for example 2 or 4), or the word tab. Ignored by minify, validate, and analyze.2
sortKeysNoWhen true, sort object keys alphabetically (recursively) before formatting. Applies to format only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
isValidNoWhether the input parsed as valid JSON.
errorNoParse error message when isValid is false, otherwise null.
outputNoProcessed result: pretty JSON, minified JSON, an analysis report, or empty for validate and blank input.
validationNoValidity plus size metrics for the submitted text.
analysisNoStructure statistics computed from the parsed JSON.
jsonPathsNoPer-node path and type entries describing the document structure.
Behavior5/5

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

Beyond annotations (readOnly, non-destructive), the description adds important behavioral traits: 'runs locally on the text you provide', 'rate-limited (60 requests/minute for anonymous callers)', and details about return values including validity flag and parse error. No contradiction with annotations.

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?

Two paragraphs: first is a concise summary, second adds detail. Every sentence adds value. Could be slightly shorter but well-organized and front-loaded.

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?

Given 5 parameters with enums and an existing output schema, the description fully covers what the tool does, including return fields (output string, validity, error, analysis, statistics). No gaps identified.

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 baseline is 3. The description adds value by explaining edge cases (e.g., blank input returns isValid false) and parameter interactions (e.g., indent ignored for non-format operations). However, the schema already provides strong descriptions.

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 explicitly states it works with JSON documents for formatting, minifying, validating, and analyzing. It distinguishes itself from sibling tools like format_json_visualizer (interactive tree), webdev_code_formatter (HTML/CSS/JS), and webdev_json_to_csv (conversion).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance: use this tool for 'plain text-in/text-out cleanup and syntax checking', and specifies alternatives when other operations are needed, such as browsing as a tree or converting to CSV.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server