Skip to main content
Glama

get_spacetrack_gp_history

Retrieve historical orbital element sets from SpaceTrack for tracking satellite orbital evolution over time. Filter by NORAD ID, name, or epoch range, and decimate results to reduce data volume.

Instructions

Query historical GP records from SpaceTrack.

Unlike get_spacetrack_gp which returns only the latest element set, this tool returns all historical element sets for matching objects. Useful for tracking orbital evolution over time.

At least one filter parameter must be provided. An epoch_range is strongly recommended to avoid very large result sets. For queries spanning more than a couple of days, use the decimation parameter to thin results (e.g. '1d' for ~1 record per day).

Requires SPACETRACK_USER and SPACETRACK_PASS environment variables.

Args: norad_cat_id: NORAD catalog number (e.g. 25544 for ISS). name: Satellite name substring search (case-insensitive). epoch_range: ISO datetime range string "start--end" to filter by EPOCH (e.g. "2024-01-01--2024-01-31"). limit: Maximum number of records to return. decimation: Thin results to ~1 record per interval. Accepts a number followed by a unit: s (seconds), m (minutes), h (hours), d (days), w (weeks). Examples: "1d", "12h", "1w".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
limitNo
decimationNo
epoch_rangeNo
norad_cat_idNo
Behavior4/5

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

With no annotations, the description fully discloses behavioral traits: returns all historical element sets, requires environment variables, warns about large result sets, and recommends decimation. It does not cover rate limits or return format details, but the provided context is strong.

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 well-structured: starts with purpose, then usage notes, requirements, and parameter list. It is clear and informative, though slightly lengthy; every sentence earns its place.

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?

Given no output schema, the description does not specify the return format or fields. It mentions 'returns all historical element sets' but lacks details on what each record contains. For a complex tool with many siblings, this is a gap.

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

Parameters5/5

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

All five parameters are explained with descriptions and examples, including format for epoch_range and decimation. Since schema description coverage is 0%, the description fully compensates, adding meaning beyond 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 clearly states the tool queries historical GP records from SpaceTrack and explicitly distinguishes it from get_spacetrack_gp by noting the latter returns only the latest element set. This provides a specific verb+resource with sibling differentiation.

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?

The description states when to use ('useful for tracking orbital evolution over time'), requires at least one filter parameter, strongly recommends an epoch_range, and suggests decimation for large queries. It lacks explicit when-not-to-use guidance but implies alternatives via sibling context.

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