qso-graph-contest-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.
IN DEVELOPMENT — this server has no working tools yet, and calling it will not answer questions about amateur radio contest calendar and rules mcp server. Planned: Which contests are running now, what is coming, and the rules, exchange and multipliers for each — with every contest citing the sponsor that published its rules. Named for this project rather than any sponsor: a server covering many sponsors' contests cannot take one sponsor's name. Progress: https://github.com/qso-graph/qso-graph-devel/issues/49
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get this server's version and development status. |
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 tool-to-tool confusion, and get_version_info has a clear, distinct meaning. It can't score a 5 since there's no set to differentiate.
The single tool follows a clean, predictable verb_noun pattern (get_version_info). Consistency is trivially satisfied but the convention itself is clear and readable.
A server named qso-graph-contest-mcp implies contest/QSO graph querying functionality, yet offers only one metadata tool. This is an extreme mismatch between the apparent scope and the surface.
No contest, QSO, or graph operations exist—no query, ingest, or aggregation tools. The only tool returns server version/development status, so agents cannot perform any domain workflow.