JSON MCP Server
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryC | Query JSON data using JSONPath syntax |
| filterC | Filter JSON data using conditions |
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 2 tools
Both tools operate on JSON data to extract subsets, and 'filter' is essentially a restricted form of JSONPath querying, so an agent could reasonably pick either for a filtering need. The descriptions do differentiate them by mechanism (JSONPath syntax vs. conditions), which helps, but the boundary is fuzzy.
Both names are single lowercase verbs (query, filter) following the exact same convention. There is no mixing of styles or verb forms.
Two tools is thin for a server whose domain (JSON manipulation) typically involves parsing, validation, transformation, and mutation. It is defensible for a narrowly scoped read-only query server, but borderline.
The surface offers only read/extract operations; there is no parsing, validation, path construction, or any modification of JSON (set/merge/delete). Agents needing to inspect or transform JSON beyond querying and filtering will hit dead ends.