json-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_jsonA | Parse and validate strict JSON. Local files/strings only. Does not fetch URLs or contact external services. |
| validate_jsoncA | Parse JSONC (comments + trailing commas) and validate. Local files/strings only. Does not fetch URLs or contact external services. |
| json_getA | Get a value at a jq-like path (e.g. .foo.bar[0]). Local files/strings only. Does not fetch URLs or contact external services. |
| json_setA | Set a value at a jq-like path; returns updated JSON (optionally write file). Local files/strings only. Does not fetch URLs or contact external services. |
| pretty_jsonB | Pretty-print JSON with indentation. Local files/strings only. Does not fetch URLs or contact external services. |
| minify_jsonA | Minify JSON to one line. Local files/strings only. Does not fetch URLs or contact external services. |
| schema_validateA | Validate JSON data against a JSON Schema using Ajv. Local files/strings only. Does not fetch URLs or contact external services. |
| diff_jsonB | Diff two JSON documents (canonical key-sorted stringify, line-oriented). Local files/strings only. Does not fetch URLs or contact external services. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: validation (strict vs JSONC), get/set by path, formatting (pretty/minify), schema validation, and diffing. No two tools overlap in functionality.
Most tools follow a verb_noun pattern (validate_json, pretty_json, minify_json, diff_json), but json_get and json_set reverse the order to noun_verb, creating a minor inconsistency. Overall the pattern is readable and predictable.
Eight tools cover a focused domain of JSON utilities without redundancy. This count is well-scoped for the server's purpose.
The tool surface covers the core lifecycle of JSON manipulation: validation, access, modification, formatting, schema checking, and comparison. No obvious gaps for the stated domain.