JSON Query 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| json_query_jsonpathB | Query a JSON file using JSONPath. Use to get values precisely from large JSON files. |
| json_query_search_keysA | Search for keys in a JSON file. Use when you do not know the path to a key in a large JSON file, but have some idea what the key is. |
| json_query_search_valuesA | Search for values in a JSON file. Use when you do not know the path to a value in a large JSON file, but have some idea what the value is. |
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 3 tools
Each tool has a clearly distinct purpose: json_query_jsonpath targets precise path-based queries, json_query_search_keys focuses on key discovery, and json_query_search_values handles value discovery. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the query need.
All tool names follow a consistent verb_noun pattern with 'json_query_' as a prefix, followed by specific descriptors (jsonpath, search_keys, search_values). This uniformity enhances readability and predictability across the tool set.
With 3 tools, the server is well-scoped for JSON querying, covering path-based queries, key searches, and value searches. However, it might be slightly thin if more advanced operations like filtering or transformation are expected, but it reasonably covers core query needs.
The tools provide comprehensive coverage for querying JSON files, including precise path queries and exploratory searches for keys and values. A minor gap exists in lacking tools for JSON manipulation (e.g., update or delete), but this is acceptable given the server's focus on querying rather than editing.