MCP JSONDiff Kel
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jsonDiffD | 执行json对比 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a distinct and clear purpose focused on JSON comparison.
The tool name 'jsonDiff' follows a consistent pattern (camelCase) and clearly describes its function. Since there is only one tool, there are no inconsistencies to evaluate.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a JSON diff server, one tool might suffice for basic comparison, but it feels thin and lacks supporting operations.
The tool covers the core function of JSON comparison, which aligns with the server's name. However, there are notable gaps, such as missing tools for handling different diff formats, merging JSON, or validating JSON inputs, which could limit agent workflows.