Skip to main content
Glama

Satellite passes over a place

perigee_passes
Read-only

When an Earth satellite (ISS = 25544, Tiangong = 48274, Hubble = 20580, or any NORAD number) passes over a place: rise, highest point and set times with direction (azimuth, compass point) and elevation, and whether it can be seen with the naked eye (sunlit satellite, dark sky) and when. Give the place's latitude and longitude (degrees, east positive) and, for local times, its IANA time zone. Up to 3 days ahead. Perigee does no geocoding: work out the coordinates and time zone yourself. For the whole night's highlights at once, use perigee_tonight.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "perigee_passes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObject id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf planet name), e.g. "25544" for the ISS.
daysNoSearch length in days (default 3).
langNoLanguage of names and texts (default en).
startNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
height_mNoObserver height above sea level, m.
latitudeYesObserver latitude, degrees (north positive).
longitudeYesObserver longitude, degrees (east positive).
time_zoneNoIANA time zone for local times, e.g. "America/Toronto".
min_elevationNoLowest culmination kept and lowest elevation counted as visible, degrees (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Object id from perigee_find (NORAD number, mission id, planet, \"moon:<id>\", \"site:<id>\", \"launch:<id>\", \"star:<id>\", \"comet:<id>\", \"asteroid:<id>\" or a dwarf planet name), e.g. \"25544\" for the ISS."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld, so the description carries the real burden and does so: it explains the visibility model (sunlit satellite + dark sky), the 3-day lookahead limit, the no-geocoding constraint, and roughly what is returned. It stops short of covering edge cases such as zero passes in range or how results are ordered.

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?

The purpose and output list come first, then the required inputs, then the constraint and the sibling pointer — good front-loading with no filler sentences. The long parenthetical ID list makes the opening clause dense, but every element is functional.

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?

For a 9-parameter, no-output-schema tool, the description covers what it returns, what inputs matter, the time horizon and the geocoding caveat. The remaining gap is minor: several optional parameters (height_m, min_elevation, lang) are not mentioned, though the schema documents them fully.

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

Parameters4/5

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

Schema coverage is already 100%, so baseline is 3; the description earns more by supplying concrete object IDs (ISS = 25544, Tiangong = 48274, Hubble = 20580) and restating that longitude is east-positive and the time zone must be IANA for local times. It does not explain the roles of height_m, min_elevation, lang, or start, leaving those to the schema.

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?

The description names a specific verb and resource — computing a satellite's rise, culmination and set over a place — and enumerates the outputs (azimuth, compass point, elevation, naked-eye visibility). It also distinguishes itself from perigee_tonight by naming that sibling for night-wide highlights.

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

Usage Guidelines5/5

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

It gives explicit conditions: use this for one object's passes, use perigee_tonight for the whole night's highlights, and supply coordinates/time zone yourself because 'Perigee does no geocoding'. The 'Up to 3 days ahead' note sets a horizon for when it is applicable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources