Skip to main content
Glama
Sign In
io.github.qso-graph/eme-mcp

io.github.qso-graph/eme-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Eme Path Loss

eme_path_loss
Read-onlyIdempotent

Calculate Earth-Moon-Earth path loss for a chosen band or frequency, at the current time or a specified UTC time, optionally from your grid locator.

Instructions

What the path to the moon and back costs, now or at a given time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eme_path_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNo2m, 70cm or 23cm. Ignored if frequency_mhz is given.70cm
whenNoUTC time (ISO 8601). Default now.
locatorNoYour grid square. Given one, the range is topocentric — from where you are, not from the Earth's centre, which differs by up to about 1.7% as the moon rises and sets.
frequency_mhzNoAn exact frequency, for a band this does not name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds that results are time-dependent and can be computed for 'now', which is useful context. It doesn't disclose output shape, but an output schema exists, so this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler, and the temporal scope is front-loaded. The metaphorical 'costs' is less precise than 'path loss', but the title covers that.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a rich schema, full annotations, and an output schema, the description only needs to orient the agent, which it does. The main gap is not clarifying the relationship to the other eme_* tools (degradation, moon window, calendar).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains band, when, locator, and frequency_mhz with details including the topocentric-range effect. The description adds only the notion of 'now or at a given time', which duplicates the schema's 'Default now'. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'What the path to the moon and back costs' conveys Earth-Moon-Earth path loss but uses metaphorical language ('costs') rather than a specific verb+resource. It conveys the domain (EME path loss) and that it can be computed for now or a given time, but it doesn't clearly distinguish this from siblings like eme_degradation or eme_moon_window.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this tool versus alternatives. The phrase 'now or at a given time' hints at the temporal parameter but no when-not or alternative-tool routing is provided, and nothing indicates whether this is the right tool for link-budget planning vs degradation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools