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…

Instructions

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 10 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. First observedv1.10.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real context on top: the 10-day forward horizon, that local times depend on the supplied time zone, and the visibility criterion (sunlit satellite against dark sky). It does not discuss rate limits, upstream data source, or response shape, but for a read-only lookup that is a minor omission.

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 output content is front-loaded in the first clause, followed by inputs, then the sibling alternative — a logical order with little waste. The parenthetical id list and coordinate conventions make the first two sentences dense, but every clause carries operational information.

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 tool with no output schema, the description does the necessary work of describing what comes back (times, directions, elevations, visibility windows) and the temporal limit. The remaining gap is that the id field's schema allows planets, moons, stars, comets, and sites while the description frames the tool purely around Earth satellites, so the non-satellite behavior is unexplained.

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 100%, so the baseline is 3, but the description still adds meaning: concrete NORAD ids for common satellites, the east-positive/degrees convention for coordinates, and the requirement that time_zone be IANA for local times. It leaves min_elevation, height_m, and lang entirely to the schema, so it is not a full 5.

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 states a specific verb and resource — satellite passes over a place — and enumerates exactly what is returned (rise, culmination, set, azimuth/compass, elevation, naked-eye visibility). It anchors the scope with concrete object examples (ISS = 25544, Tiangong = 48274, Hubble = 20580), so an agent can distinguish it from generic object/orbit tools without opening the schema.

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 names the alternative explicitly — 'For the whole night's highlights at once, use perigee_tonight' — and states the selecting condition. It also gives prerequisites (supply latitude/longitude and an IANA time zone for local times) and an explicit exclusion ('Perigee does no geocoding: work out the coordinates and time zone yourself'), which prevents a common failure mode.

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