mcp-v2-minimal
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.
Two small utilities. Use json_format to normalise JSON the user pasted, and echo to verify the connection.
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 |
|---|---|
| echoA | Return the text you pass in. Use this to confirm a host is actually connected. |
| json_formatA | Parse JSON and return it pretty-printed with a stable key order. Returns a readable error instead of throwing when the input is not valid 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 2 tools
The two tools have completely non-overlapping purposes: one is a connectivity check that echoes input, the other parses and reformats JSON. An agent could not reasonably confuse them.
Both names are lowercase snake_case, which is consistent, but the patterns differ: 'echo' is a bare verb while 'json_format' is a noun_verb compound. With only two tools there is no discernible shared convention to rely on.
Two tools is borderline thin — the server presents itself as a 'minimal' utility host, so a small surface is intentional, but there is very little substance beyond a ping and one formatter.
The surface covers its two narrow utilities but leaves obvious adjacent gaps: no JSON validation/minification/query, and no other basic text or connectivity operations. Each tool is a dead end on its own rather than part of a coherent utility set.