Skip to main content
Glama

astronomy-mcp-server: get satellite passes

astronomy_get_satellite_passes
Read-onlyIdempotent

Predict visible passes of a satellite (e.g. the ISS, NORAD 25544) over an observer in the next days. Identify the satellite by exactly one of norad_id or name — supplying both, or neither, is rejected. A few well-known common names resolve directly to their catalog numbers, ignoring case: ISS or International Space Station (25544), Hubble, Hubble Space Telescope, or HST (20580), and Tiangong, CSS, or Chinese Space Station (48274). Any other name is matched as a case-insensitive substring of CelesTrak's catalog names, so it resolves only when it picks out a single object: a broader query comes back with the matching objects and their catalog numbers to choose from. Either way the result echoes the query that resolved it as resolved_from_name. Fetches the object's current GP element set from CelesTrak, propagates it with SGP4 in-process, and returns each pass's rise, peak, and set times with azimuths and the peak elevation, plus the stretch of the pass visible to the naked eye: visible_start_utc through visible_end_utc, with the elevation and azimuth at each end. A pass is returned when that visible stretch — the satellite above the horizon and sunlit while the Sun is below −6° for the observer — reaches 10° elevation, wherever in the pass it falls. sunlit reports illumination at the peak instant, so it is false on a pass seen only before it enters Earth's shadow or after it leaves. Rise, set, and the visible-stretch edges are within 1 s of the true instants; the peak is the highest sample of a 30-second scan. Every returned pass rises in the requested window or in the 30 s before start: a pass up longer than that at start is omitted rather than reported with start as its rise, so back up start to see it, while a pass still up when the window ends is reported through its actual set. Searches at most 10 days per call: a larger days, up to 30, searches the first 10 and returns a notice naming the exact start and days that continue the search with no pass repeated or skipped, while that start stays within about a month of the element set's epoch. A start further than about a month from the element set's epoch is rejected as out of range on that distance alone, and an element set that will not propagate to a window inside that horizon is rejected as a reentry — so an empty passes means only that nothing was visible. CelesTrak publishes only current element sets, so in practice start must be within about a month of today. NORAD catalog numbers and catalog names are found at celestrak.org or heavens-above.com. This is a gated, network-backed extension (CelesTrak is keyless but rate-limited; element sets are cached briefly). Default elevation 0 m; pass an IANA timezone for observer-local pass times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days ahead to search for passes. Default 7. At most 10 are searched per call; a value up to 30 searches the first 10 with a notice naming the `start` and `days` that continue the search.
nameNoSatellite name to resolve, e.g. "ISS (ZARYA)". The common names ISS, International Space Station, Hubble, Hubble Space Telescope, HST, Tiangong, CSS, and Chinese Space Station resolve directly to their catalog numbers, ignoring case and surrounding whitespace. Any other name is matched against CelesTrak as a case-insensitive substring of the catalog name, so give the fullest name you have — a short one matches many objects and is rejected as ambiguous. Mutually exclusive with `norad_id` — supply exactly one.
startNoSearch start as an ISO 8601 UTC string, within about a month of the current element set's epoch — for a tracked object that epoch is hours old, so in practice within about a month of today. A start further out is rejected rather than answered from elements that no longer describe the orbit. Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process.
latitudeYesObserver latitude in decimal degrees, north positive.
norad_idNoNORAD catalog number of the satellite, e.g. 25544 for the ISS. Found at celestrak.org or heavens-above.com. Mutually exclusive with `name` — supply exactly one.
timezoneNoIANA timezone for localized pass times, e.g. "America/Los_Angeles". When omitted, output is UTC-only.
elevationNoObserver elevation in meters above sea level. Default 0.
longitudeYesObserver longitude in decimal degrees, east positive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoHow to search the days the per-call cap held back: the exact `start` and `days` to re-call with, or — when that start would lie more than about a month from the element set's epoch — that no call can search them. Absent when every requested day was searched.
passesNoPasses whose visible stretch — the satellite above the horizon and sunlit while the Sun is below −6° for the observer — reaches 10° elevation, in the window searched, chronological.
norad_idNoThe NORAD catalog number echoed from the request.
totalCountNoNumber of visible passes found in the window searched.
satellite_nameNoSatellite name as CelesTrak catalogs it (the element set's OBJECT_NAME).
resolved_from_nameNoThe name query that resolved this object. Present only when the request supplied `name` rather than `norad_id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Number of days ahead to search for passes. Default 7, max 10."New value: +"Number of days ahead to search for passes. Default 7. At most 10 are searched per call; a value up to 30 searches the first 10 with a notice naming the `start` and `days` that continue the search."
    • changedInput schema / properties / days / maximum
      Previous value: -10New value: +30
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_time`: The start timestamp is not a parseable ISO 8601 instant, or names a calendar date that does not exist (e.g. 2026-02-30). `time_out_of_range`: The start instant is outside the SGP4 high-accuracy span (≈1900–2100), or more than about a month from the epoch of the current element set — checked on the epoch distance itself, since SGP4 keeps returning positions well past the point where the mean elements describe the orbit. `invalid_timezone`: The `timezone` value is not an IANA zone this runtime knows. `invalid_target`: Neither `norad_id` nor `name` was supplied, or both were. `tle_not_found`: CelesTrak has no current element set for the NORAD ID. `satellite_name_not_found`: No current CelesTrak object has a name containing the `name` value. `ambiguous_satellite_name`: The `name` value matches more than one current object and none of them carries it as their whole name. The error names the match count and lists the matching objects with their catalog numbers, capped when there are more than the list holds. A capped list carries a hint leading with narrowing instead of with the list, since the wanted object need not be among the ones shown. `object_decayed`: A current element set will not propagate to a window near its own epoch — the signature of an object that has reentered. `celestrak_unavailable`: The element-set fetch failed after retries, or returned a body that is not JSON at all. `malformed_element_set`: CelesTrak answered with parsable JSON whose GP record does not carry the fields an OMM element set requires — a permanent property of that record, not the transient outage celestrak_unavailable covers. The same request returns the same record, so retrying it can only fail again. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_time`: The start timestamp is not a parseable ISO 8601 instant, or names a calendar date that does not exist (e.g. 2026-02-30). `time_out_of_range`: The start instant falls outside the years 1900–2100, or more than about a month from the epoch of the current element set — checked on the epoch distance itself, since SGP4 keeps returning positions well past the point where the mean elements describe the orbit. `invalid_timezone`: The `timezone` value is not an IANA zone this runtime knows. `invalid_target`: Neither `norad_id` nor `name` was supplied, or both were. `tle_not_found`: CelesTrak has no current element set for the NORAD ID. `satellite_name_not_found`: No current CelesTrak object has a name containing the `name` value. `ambiguous_satellite_name`: The `name` value matches more than one current object and none of them carries it as their whole name. The error names the match count and lists the matching objects with their catalog numbers, capped when there are more than the list holds. A capped list carries a hint leading with narrowing instead of with the list, since the wanted object need not be among the ones shown. `object_decayed`: A current element set will not propagate to a window near its own epoch — the signature of an object that has reentered. `celestrak_unavailable`: The element-set fetch failed after retries, or returned a body that is not JSON at all. `malformed_element_set`: CelesTrak answered with parsable JSON whose GP record does not carry the fields an OMM element set requires — a permanent property of that record, not the transient outage celestrak_unavailable covers. The same request returns the same record, so retrying it can only fail again. Other values are possible when a failure originates below the handler."
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "How to search the days the per-call cap held back: the exact `start` and `days` to re-call with, or — when that start would lie more than about a month from the element set's epoch — that no call can search them. Absent when every requested day was searched.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / passes / description
      Previous value: -"Visible passes (sunlit satellite over a dark-enough sky) in the requested window, chronological."New value: +"Passes whose visible stretch — the satellite above the horizon and sunlit while the Sun is below −6° for the observer — reaches 10° elevation, in the window searched, chronological."
    • changedOutput schema / properties / passes / items / description
      Previous value: -"One visible pass with rise/peak/set geometry and illumination."New value: +"One visible pass: horizon-to-horizon rise/peak/set geometry, illumination at peak, and the stretch of the pass that is visible to the naked eye."
    • changedOutput schema / properties / passes / items / properties / duration_seconds / description
      Previous value: -"Pass duration from rise to set, in seconds."New value: +"Pass duration from `rise_utc` to `set_utc`, in seconds."
    • changedOutput schema / properties / passes / items / properties / peak_altitude_degrees / description
      Previous value: -"Maximum elevation angle during the pass, in degrees."New value: +"Maximum elevation angle during the pass, in degrees, as sampled every 30 seconds."
    • changedOutput schema / properties / passes / items / properties / peak_utc / description
      Previous value: -"Time of maximum elevation in ISO 8601 UTC."New value: +"Time of maximum elevation in ISO 8601 UTC, the highest sample of a 30-second scan."
    • changedOutput schema / properties / passes / items / properties / rise_azimuth_degrees / description
      Previous value: -"Azimuth at rise, in degrees (0=N, 90=E, 180=S, 270=W)."New value: +"Azimuth at `rise_utc`, in degrees (0=N, 90=E, 180=S, 270=W)."
    • changedOutput schema / properties / passes / items / properties / rise_utc / description
      Previous value: -"Acquisition of signal (rise above horizon) in ISO 8601 UTC."New value: +"Rise above the horizon in ISO 8601 UTC, within 1 s of the true crossing. Can fall up to 30 s before `start` when the satellite rose inside the 30-second scan step ending at `start`."
    • changedOutput schema / properties / passes / items / properties / set_azimuth_degrees / description
      Previous value: -"Azimuth at set, in degrees."New value: +"Azimuth at `set_utc`, in degrees."
    • changedOutput schema / properties / passes / items / properties / set_utc / description
      Previous value: -"Loss of signal (set below horizon) in ISO 8601 UTC."New value: +"Set below the horizon in ISO 8601 UTC, within 1 s of the true crossing."
    • changedOutput schema / properties / passes / items / properties / sunlit / description
      Previous value: -"True when the satellite is in sunlight at peak — a precondition for naked-eye visibility."New value: +"True when the satellite is in sunlight at the peak instant. False on a pass that enters Earth's shadow before its peak or leaves it after — the visible_* fields say when it can be seen."
    • addedOutput schema / properties / passes / items / properties / visible_end_altitude_degrees
      Added value: +{
      +  "description": "Elevation where the visible stretch ends, in degrees — 0 when it ends at the set.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_end_azimuth_degrees
      Added value: +{
      +  "description": "Azimuth where the visible stretch ends, in degrees.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_end_local
      Added value: +{
      +  "description": "Visible-stretch end in observer-local time, present only when a timezone was supplied.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_end_utc
      Added value: +{
      +  "description": "End of the visible stretch in ISO 8601 UTC. Equals `set_utc` when the pass is visible until it sets; otherwise within 1 s of the moment it enters Earth's shadow or the sky brightens.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_start_altitude_degrees
      Added value: +{
      +  "description": "Elevation where the visible stretch starts, in degrees — 0 when it starts at the rise.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_start_azimuth_degrees
      Added value: +{
      +  "description": "Azimuth where the visible stretch starts, in degrees — where to look first.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_start_local
      Added value: +{
      +  "description": "Visible-stretch start in observer-local time, present only when a timezone was supplied.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / passes / items / properties / visible_start_utc
      Added value: +{
      +  "description": "Start of the visible stretch — above the horizon, sunlit, over a dark sky — in ISO 8601 UTC. Equals `rise_utc` when the pass is visible from its rise; otherwise within 1 s of the moment it leaves Earth's shadow or the sky darkens.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / passes / items / required
      Previous value: -[
      -  "rise_utc",
      -  "peak_utc",
      -  "set_utc",
      -  "peak_altitude_degrees",
      -  "rise_azimuth_degrees",
      -  "set_azimuth_degrees",
      -  "peak_azimuth_degrees",
      -  "duration_seconds",
      -  "sunlit"
      -]New value: +[
      +  "rise_utc",
      +  "peak_utc",
      +  "set_utc",
      +  "peak_altitude_degrees",
      +  "rise_azimuth_degrees",
      +  "set_azimuth_degrees",
      +  "peak_azimuth_degrees",
      +  "duration_seconds",
      +  "sunlit",
      +  "visible_start_utc",
      +  "visible_end_utc",
      +  "visible_start_altitude_degrees",
      +  "visible_end_altitude_degrees",
      +  "visible_start_azimuth_degrees",
      +  "visible_end_azimuth_degrees"
      +]
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of visible passes found in the window."New value: +"Number of visible passes found in the window searched."
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Satellite name to resolve against CelesTrak, e.g. \"ISS (ZARYA)\". Matched as a case-insensitive substring of the catalog name, so give the fullest name you have — a short one matches many objects and is rejected as ambiguous. Mutually exclusive with `norad_id` — supply exactly one."New value: +"Satellite name to resolve, e.g. \"ISS (ZARYA)\". The common names ISS, International Space Station, Hubble, Hubble Space Telescope, HST, Tiangong, CSS, and Chinese Space Station resolve directly to their catalog numbers, ignoring case and surrounding whitespace. Any other name is matched against CelesTrak as a case-insensitive substring of the catalog name, so give the fullest name you have — a short one matches many objects and is rejected as ambiguous. Mutually exclusive with `norad_id` — supply exactly one."
  3. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "norad_id",
      +      "passes",
      +      "totalCount"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `invalid_time`: The start timestamp is not a parseable ISO 8601 instant, or names a calendar date that does not exist (e.g. 2026-02-30). `time_out_of_range`: The start instant is outside the SGP4 high-accuracy span (≈1900–2100), or more than about a month from the epoch of the current element set — checked on the epoch distance itself, since SGP4 keeps returning positions well past the point where the mean elements describe the orbit. `invalid_timezone`: The `timezone` value is not an IANA zone this runtime knows. `invalid_target`: Neither `norad_id` nor `name` was supplied, or both were. `tle_not_found`: CelesTrak has no current element set for the NORAD ID. `satellite_name_not_found`: No current CelesTrak object has a name containing the `name` value. `ambiguous_satellite_name`: The `name` value matches more than one current object and none of them carries it as their whole name. The error names the match count and lists the matching objects with their catalog numbers, capped when there are more than the list holds. A capped list carries a hint leading with narrowing instead of with the list, since the wanted object need not be among the ones shown. `object_decayed`: A current element set will not propagate to a window near its own epoch — the signature of an object that has reentered. `celestrak_unavailable`: The element-set fetch failed after retries, or returned a body that is not JSON at all. `malformed_element_set`: CelesTrak answered with parsable JSON whose GP record does not carry the fields an OMM element set requires — a permanent property of that record, not the transient outage celestrak_unavailable covers. The same request returns the same record, so retrying it can only fail again. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "invalid_time",
      +            "time_out_of_range",
      +            "invalid_timezone",
      +            "invalid_target",
      +            "tle_not_found",
      +            "satellite_name_not_found",
      +            "ambiguous_satellite_name",
      +            "object_decayed",
      +            "celestrak_unavailable",
      +            "malformed_element_set"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "norad_id",
      -  "passes",
      -  "totalCount"
      -]
  4. Changed1 schema field changed
    • changedInput schema / properties / start / description
      Previous value: -"Search start as an ISO 8601 UTC string, within about a month of the current element set's epoch — for a tracked object that epoch is hours old, so in practice within about a month of today. A start further out is rejected rather than answered from elements that no longer describe the orbit. Defaults to now."New value: +"Search start as an ISO 8601 UTC string, within about a month of the current element set's epoch — for a tracked object that epoch is hours old, so in practice within about a month of today. A start further out is rejected rather than answered from elements that no longer describe the orbit. Defaults to now. A value with no zone designator is read as UTC, not the local zone of the server process."
  5. Changed1 schema field changed
    • changedInput schema / properties / start / description
      Previous value: -"Search start as an ISO 8601 UTC string, within about a month of today — the current element set cannot be propagated further. Defaults to now."New value: +"Search start as an ISO 8601 UTC string, within about a month of the current element set's epoch — for a tracked object that epoch is hours old, so in practice within about a month of today. A start further out is rejected rather than answered from elements that no longer describe the orbit. Defaults to now."
  6. Changed6 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "name"
      +      ]
      +    },
      +    "required": [
      +      "norad_id"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "not": {
      +      "required": [
      +        "norad_id"
      +      ]
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Satellite name to resolve against CelesTrak, e.g. \"ISS (ZARYA)\". Matched as a case-insensitive substring of the catalog name, so give the fullest name you have — a short one matches many objects and is rejected as ambiguous. Mutually exclusive with `norad_id` — supply exactly one.",
      +  "type": "string"
      +}
    • changedInput schema / properties / norad_id / description
      Previous value: -"NORAD catalog number of the satellite, e.g. 25544 for the ISS. Found at celestrak.org or heavens-above.com."New value: +"NORAD catalog number of the satellite, e.g. 25544 for the ISS. Found at celestrak.org or heavens-above.com. Mutually exclusive with `name` — supply exactly one."
    • changedInput schema / required
      Previous value: -[
      -  "norad_id",
      -  "latitude",
      -  "longitude"
      -]New value: +[
      +  "latitude",
      +  "longitude"
      +]
    • addedOutput schema / properties / resolved_from_name
      Added value: +{
      +  "description": "The name query that resolved this object. Present only when the request supplied `name` rather than `norad_id`.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / satellite_name / description
      Previous value: -"Satellite name from the TLE header, when present."New value: +"Satellite name as CelesTrak catalogs it (the element set's OBJECT_NAME)."
  7. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Far exceeds what the readOnly/openWorld/idempotent annotations convey: it discloses CelesTrak fetch + in-process SGP4 propagation, brief element-set caching, keyless but rate-limited network dependency, rejection modes (out-of-range epoch, reentry), 1 s timing accuracy with a 30 s peak scan, and the exact visibility criterion (10° elevation, sun below −6°). This is exactly the mutation/limitation context annotations cannot supply.

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

Conciseness3/5

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

Purpose and the mutually-exclusive-key rule are front-loaded correctly, and few sentences are pure filler. But the body is a dense, run-on wall of text with heavily nested clauses ('a pass up longer than that at `start`...'), which strains scannability for an agent deciding whether to call it.

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

Completeness5/5

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

For an 8-parameter, network-backed prediction tool with an output schema, everything needed to call it correctly is present: inputs, exclusivity constraints, time-window footguns, failure semantics, and the meaning of an empty `passes`. Return-value details are covered by the output schema, so nothing material is missing.

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 baseline is 3, and the description largely restates the schema's own parameter text (name resolution rules, mutual exclusivity, days cap, start horizon, timezone, elevation default). The one genuinely additive point is that an over-broad name comes back with candidate catalog numbers, but that is already in the schema's `name` description.

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?

Opens with a specific verb and resource: 'Predict visible passes of a satellite over an observer,' with the key scope qualifier ('visible') and a concrete example (ISS, NORAD 25544). It is clearly separable from siblings like astronomy_get_rise_set or astronomy_get_sky_position, which do not predict pass windows.

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?

Gives strong situational guidance: how to supply name vs norad_id, when a name resolution fails ambiguously, when to back up `start` to catch an in-progress pass, and how the 10-day per-call cap is continued. However, it never explicitly routes the agent away from or toward any named sibling tool, so it stops short of a 5.

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.