AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

satellite_predict_passes

Predict upcoming Meteor-M passes over your location, including rise/set times, peak elevation, and azimuths, to decide when to start satellite decoding.

Instructions

Predict upcoming Meteor-M passes over a location (rise/set times, peak elevation, azimuths) using current orbital elements from Celestrak. Needs network access. Use it to decide when to run satellite_decode_meteor.

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": "satellite_predict_passes"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	No	Look-ahead window in hours (max 168)
`latitude`	No	Optional override of the observer latitude; normally auto-detected
`longitude`	No	Optional override of the observer longitude; normally auto-detected
`satellite`	No		METEOR-M2-4
`altitude_m`	No	Observer altitude in metres
`min_elevation`	No	Only report passes whose peak elevation reaches this many degrees

Output Schema

Name	Required	Description	Default
`passes`	No
`elements`	No
`satellite`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose two non-obvious traits: it requires network access and it pulls current orbital elements from Celestrak, meaning results depend on external freshness. It does not describe failure behavior when offline or Celestrak is unreachable, which is the main remaining gap for a network-bound tool.

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

Conciseness5/5

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

Three short sentences, front-loaded with what the tool produces, then the operational constraint, then the usage pointer. No redundant or filler wording.

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?

An output schema exists so return values need not be explained, yet the description still summarizes them usefully. Combined with the network dependency note and the sibling linkage, an agent has enough to call this correctly; only external-failure behavior is left implicit.

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 83%, so the parameters are already well documented, and the description adds nothing beyond that. It does not mention the look-ahead window, the minimum elevation filter, or the latitude/longitude auto-detect override behavior, all of which affect results materially.

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

Purpose5/5

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

Specific verb ("Predict") plus resource ("upcoming Meteor-M passes over a location") and an explicit enumeration of what is returned (rise/set times, peak elevation, azimuths). It also names the sibling tool it feeds into, so an agent can distinguish it from satellite_decode_meteor and satellite_get_status without opening either schema.

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

Usage Guidelines4/5

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

Explicitly states the use case ("Use it to decide when to run satellite_decode_meteor"), which gives a concrete downstream routing decision. It does not state when-not to use it or what to do if a pass window is empty, but the positive guidance is clear and actionable.

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