Skip to main content
Glama

search_satellites

Read-only

Search the satellite catalog by name, operator, country, orbit class, status, object type, launch or decay dates, COSPAR, or NORAD ID, and return match counts for fleet and segment queries.

Instructions

Search the satellite catalog (UCS + Space-Track SATCAT) by name, operator, country, orbit class, status, object type, launch or decay date range, COSPAR, or NORAD id. Joined to the resolved operator entity. Every response includes total, the full number of matching objects (rows are capped at 500 per call; page with offset), so answer counting questions from total — set count_only=true to skip the rows. Combine filters in one call instead of splitting the search, e.g. a constellation's payloads launched in a given year: name=, object_type=payload, launched_after=-01-01, launched_before=-12-31, count_only=true. Use for counting a fleet or a segment, 'what does SpaceX have in LEO?', 'find NORAD 44713', or building an operator's fleet.

Input Schema

NameRequiredDescriptionDefault
nameNoSubstring match on satellite name or alternate names, ignoring case, accents, spaces and punctuation (NOAA-16 matches NOAA 16 DEB)
sortNoRow order: launch_date, decay_date, name or norad, ascending; prefix - for descending (default -launch_date, newest first)
limitNoMax rows returned (default 50, max 500). total always reports the full match count regardless of limit; page with offset. Output keeps the rows that fit in about 40 KB and says how many it left out
noradNoNORAD catalog id (integer)
cosparNoCOSPAR / international designator: a full one (1998-067A) matches that object; a launch designator without the piece letter (1998-067) matches every object from that launch
offsetNoRows to skip, for paging past the first limit rows (keep the same filters and sort)
statusNoOrbital status: active (on orbit) or decayed; matches every catalog spelling of each
countryNoOperator country as a code or name: US, China (PRC, CN), Russia (CIS, RU), UK, Japan, India, France, Germany and ~40 more match every spelling the catalog uses for that country; CIS covers the USSR and Russia. Other values match exactly, case-insensitively. International organisations keep their own codes (ESA, ITSO, EUTE, SES, GLOB, ORB)
operatorNoSubstring match on operator name (e.g. SpaceX); note many rows use a country code (US, CIS, PRC) as the operator
entity_idNoFilter by resolved operator entity UUID
count_onlyNoReturn only total (the full match count), no rows. Use for any 'how many' question
object_typeNoObject type: payload, rocket_body, debris, or unknown. Use payload to count satellites rather than all cataloged objects. unknown also matches ~340 merge-era rows with no type; payload/rocket_body/debris exclude them
orbit_classNoOrbit class, exact uppercase value, one of: LEO (apogee below 2,000 km), MEO (perigee above 2,000 km and apogee below 35,000 km), GEO (perigee above 35,000 km and apogee below 36,500 km), HEO (perigee below 2,000 km and apogee above 35,000 km, e.g. GTO and Molniya), OTHER (any other orbit). Objects with no known perigee/apogee have no class and match none. Any other value returns 0 rows
decayed_afterNoDecay/reentry date on or after (YYYY-MM-DD); only decayed objects have a decay date, so this also limits results to decayed objects
decayed_beforeNoDecay/reentry date on or before (YYYY-MM-DD)
launched_afterNoLaunch date on or after (YYYY-MM-DD)
launched_beforeNoLaunch date on or before (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.10.0
    • changedInput schema / properties / cospar / description
      Previous value: -"COSPAR / international designator (exact match)"New value: +"COSPAR / international designator: a full one (1998-067A) matches that object; a launch designator without the piece letter (1998-067) matches every object from that launch"
    • changedInput schema / properties / country / description
      Previous value: -"Operator country code (exact match)"New value: +"Operator country as a code or name: US, China (PRC, CN), Russia (CIS, RU), UK, Japan, India, France, Germany and ~40 more match every spelling the catalog uses for that country; CIS covers the USSR and Russia. Other values match exactly, case-insensitively. International organisations keep their own codes (ESA, ITSO, EUTE, SES, GLOB, ORB)"
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows returned (default 50, max 500). total always reports the full match count regardless of limit. Output keeps the rows that fit in about 40 KB and says how many it left out"New value: +"Max rows returned (default 50, max 500). total always reports the full match count regardless of limit; page with offset. Output keeps the rows that fit in about 40 KB and says how many it left out"
    • changedInput schema / properties / name / description
      Previous value: -"Substring match on satellite name"New value: +"Substring match on satellite name or alternate names, ignoring case, accents, spaces and punctuation (NOAA-16 matches NOAA 16 DEB)"
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip, for paging past the first limit rows (keep the same filters and sort)",
      +  "type": "integer"
      +}
    • changedInput schema / properties / orbit_class / description
      Previous value: -"Orbit class (e.g. LEO, MEO, GEO)"New value: +"Orbit class, exact uppercase value, one of: LEO (apogee below 2,000 km), MEO (perigee above 2,000 km and apogee below 35,000 km), GEO (perigee above 35,000 km and apogee below 36,500 km), HEO (perigee below 2,000 km and apogee above 35,000 km, e.g. GTO and Molniya), OTHER (any other orbit). Objects with no known perigee/apogee have no class and match none. Any other value returns 0 rows"
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Row order: launch_date, decay_date, name or norad, ascending; prefix - for descending (default -launch_date, newest first)",
      +  "type": "string"
      +}
  2. Changed8 schema fields changedv0.7.0
    • addedInput schema / properties / count_only
      Added value: +{
      +  "description": "Return only total (the full match count), no rows. Use for any 'how many' question",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / decayed_after
      Added value: +{
      +  "description": "Decay/reentry date on or after (YYYY-MM-DD); only decayed objects have a decay date, so this also limits results to decayed objects",
      +  "type": "string"
      +}
    • addedInput schema / properties / decayed_before
      Added value: +{
      +  "description": "Decay/reentry date on or before (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / launched_after
      Added value: +{
      +  "description": "Launch date on or after (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / launched_before
      Added value: +{
      +  "description": "Launch date on or before (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 50, max 500)"New value: +"Max rows returned (default 50, max 500). total always reports the full match count regardless of limit. Output keeps the rows that fit in about 40 KB and says how many it left out"
    • addedInput schema / properties / object_type
      Added value: +{
      +  "description": "Object type: payload, rocket_body, debris, or unknown. Use payload to count satellites rather than all cataloged objects. unknown also matches ~340 merge-era rows with no type; payload/rocket_body/debris exclude them",
      +  "type": "string"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"Orbital status (e.g. active, decayed)"New value: +"Orbital status: active (on orbit) or decayed; matches every catalog spelling of each"
  3. First observedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, but the description adds important response behavior: every response includes `total` as the full match count, rows are capped at 500 per call, and paging uses offset. It also explains that `count_only=true` skips rows entirely, which is valuable operational context beyond the annotations.

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 description is dense but front-loaded with the core search capability, then moves to response behavior and examples. It is somewhat long and repeats the `total`/`count_only` paging behavior that also appears in the schema, but the repetition is purposeful and not wasteful.

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 a 17-parameter search tool with no output schema and minimal annotations, the description covers the essential context: data sources, filter combinations, response totals, row caps, paging with offset, and count-only mode. An agent has enough information to invoke it correctly without needing to inspect every parameter.

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 documents all 17 parameters thoroughly, including enums for status, object_type, and orbit_class. The description reinforces key semantics like `total` being unaffected by `limit` and the `count_only` flag, but this largely repeats what the schema already provides rather than adding new parameter meaning.

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: it searches the satellite catalog (UCS + Space-Track SATCAT) and enumerates the filterable dimensions. This clearly distinguishes it from sibling tools such as search_ground_stations and search_positions, which target different space-domain datasets.

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?

It gives explicit usage scenarios ('counting a fleet or a segment', 'what does SpaceX have in LEO?', 'find NORAD 44713') and recommends combining filters in one call rather than splitting the search. It does not explicitly name alternatives or say when not to use this 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.