JSON Analyser MCP
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_jsonD | – |
| query_jsonD | – |
| get_json_chunkD | – |
| multi_query_jsonD | – |
| get_unique_valuesD | – |
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 5 tools
The boundaries between read_json, get_json_chunk, and query_json are unclear, especially since no descriptions are provided. multi_query_json also overlaps heavily with query_json, making tool selection ambiguous without additional context.
Most tools use snake_case and a verb-first pattern, but the naming is not fully uniform: multi_query_json uses a modifier prefix, and get_unique_values lacks the _json suffix. The core pattern is readable but has notable deviations.
Five tools is a reasonable, well-scoped count for a focused JSON analysis server. Each tool appears to cover a distinct aspect of reading or querying JSON without unnecessary bloat.
The set covers common JSON analysis needs: reading, chunked access, single queries, batch queries, and unique value extraction. Minor gaps like schema inspection or validation exist, but core analytical workflows are likely covered.