Skip to main content
Glama
duncaneddy

brahe-mcp

by duncaneddy
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

plot_ground_track

Plot the ground track of a satellite on a world map by propagating its orbit. Specify satellite, start and end epochs, and optional ground stations.

Instructions

Plot satellite ground track on a world map.

Propagates the satellite and plots its sub-satellite point trace.

Args: satellite: Satellite spec dict (same format as compute_access). Must include "source" key ("tle", "gp_record", or "state"). start_epoch: Start of ground track (ISO epoch string). end_epoch: End of ground track (ISO epoch string). step_seconds: Propagation step size in seconds (default 60). ground_stations: Optional list of location dicts to plot on map. show_grid: Show latitude/longitude grid lines. show_legend: Show plot legend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_epochYes
satelliteYes
show_gridNo
show_legendNo
start_epochYes
step_secondsNo
ground_stationsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided. Description lacks details on side effects, permissions, or whether plot is displayed vs returned. Does not mention return value.

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?

Concise docstring format with clear first sentence. Args block is structured but could be trimmed slightly.

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

Completeness2/5

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

Output schema exists but not described. Missing details on return type, error cases, and prerequisites for satellite spec.

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 coverage is 0%, but description includes an Args block that explains each parameter's purpose and format, adding value beyond the schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Plot satellite ground track on a world map' and explains propagation. However, does not explicitly differentiate from sibling 'plot_ground_track_from_gp'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. Does not mention prerequisites or exclusions.

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