Skip to main content
Glama

query_gcat_satcat

Retrieve satellite records from the GCAT/SATCAT catalog using chainable filters for name, object type, owner, status, and orbital elements.

Instructions

Query GCAT SATCAT with advanced chainable filters.

At least one filter parameter must be provided. Filters are applied sequentially to narrow results. Use list_gcat_options() to see valid enumeration codes for object_type, status, etc.

Args: name: Name substring search (case-insensitive). object_type: Object type prefix — P=Payload, R1-R4=Rocket stages, D=Debris, C=Craft. Use list_gcat_options() for full codes. owner: Owner/operator organization code (e.g. "NASA", "SpX"). state: State/country code (e.g. "US", "CN", "JP", "SU"). status: Orbital status code — O=In orbit, R=Reentered, D=Deorbited, E=Escaped, C=Non-functional. Use list_gcat_options() for full codes. perigee_min: Minimum perigee altitude in km. perigee_max: Maximum perigee altitude in km. apogee_min: Minimum apogee altitude in km. apogee_max: Maximum apogee altitude in km. inc_min: Minimum inclination in degrees. inc_max: Maximum inclination in degrees. limit: Maximum number of records to return (default 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
limitNo
ownerNo
stateNo
statusNo
inc_maxNo
inc_minNo
apogee_maxNo
apogee_minNo
object_typeNo
perigee_maxNo
perigee_minNo
Behavior3/5

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

No annotations are provided, so the description must carry full burden. It mentions sequential filtering and the requirement of at least one filter but omits details on rate limits, pagination, and response format, which are relevant for a query tool.

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 structured with an Args section and key usage notes up front. It is clear but somewhat lengthy due to the parameter list; no extra sentences.

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

Completeness3/5

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

While parameters are well covered, the description lacks details on return format, pagination, and typical use cases. For a tool with 12 parameters and no output schema, more contextual information would be beneficial.

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 0%, so the description compensates by explaining each parameter's meaning (e.g., case-insensitive substring search, object type prefixes). However, the limit parameter description is minimal, and some codes are left to another tool.

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 clearly states the tool queries GCAT SATCAT with chainable filters, distinguishing it from sibling tools like get_gcat_satcat by specifying filtering capability.

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 explicitly requires at least one filter parameter and references list_gcat_options() for valid enumeration codes, guiding correct usage. However, it lacks explicit exclusions for when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/duncaneddy/brahe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server