io.github.qso-graph/eme-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.
EME (moonbounce) planning: when the moon is up from your grid, when it is up from both ends of a schedule at once, what the path costs on 2m/70cm/23cm, and which days are least degraded. Everything is computed locally from the moon's ephemeris; nothing is fetched. Start with eme_moon_window for a grid square such as DN13.
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 eme-mcp's version and the ephemeris series it computes from. |
| eme_moon_windowC | Where the moon is from a grid square, and when both ends of a schedule can see it. |
| eme_path_lossB | What the path to the moon and back costs, now or at a given time. |
| eme_degradationC | How much worse than the best case the moon is, now or at a given time. |
| eme_calendarC | The least degraded days ahead — when the moon is nearest. |
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 5 tools
Each tool targets a distinct EME concept: version/source info, visibility windows, path loss, degradation, and a calendar of favorable days. The main overlap is between eme_degradation and eme_calendar, since the calendar is essentially a ranked view of degraded days, but their timing granularities and purposes are clear enough.
Four domain tools consistently use an eme_ prefix followed by a noun phrase, which is predictable and readable. get_version_info deviates with a get_ verb-noun convention, but it is a distinct metadata tool and does not create confusion.
Five tools is well-scoped for a focused EME calculation server. Each tool maps to a clear, useful capability without obvious filler or missing major operations.
The surface covers version/source provenance, moon visibility windows, path loss, degradation, and calendar-based planning, which is solid for the apparent EME domain. Minor gaps could exist around station-specific configuration or additional link-budget terms, but core workflows are covered.