Skip to main content
Glama

Celestrak

by io.github.pipeworx-io

Get Group

get_group
Read-onlyIdempotent

List orbital elements (TLE / GP data) for an entire CelesTrak group — e.g. the Starlink, GPS, or weather satellite catalog. Groups: "stations", "starlink", "gps-ops", "weather", "science", "geo", "active". Returns up to 100 satellites with orbital parameters (inclination, eccentricity, period). Catalog/orbital data, not live tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesA CelesTrak group, e.g. "stations", "starlink", "gps-ops", "weather", "science", "geo", "active".

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context that this is catalog/orbital data, not live tracking, and specifies a limit of 100 satellites and the orbital parameters returned. No contradiction with annotations.

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

Conciseness5/5

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

The description is two sentences, each adding essential info without redundancy. Front-loaded with the core purpose, followed by specifics. Every word earns its place.

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?

Given the simple structure (1 parameter, no output schema, strong annotations), the description fully covers what the tool does, what it returns (up to 100 satellites, orbital parameters), and what it does not do (live tracking).

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 100% with a description for the 'group' parameter listing valid values. The description enhances this by providing examples and explaining the concept of groups, adding semantic value 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 uses specific verbs ('List orbital elements') and resource ('CelesTrak group'), provides concrete examples (Starlink, GPS, weather), and distinguishes from siblings like get_satellite. It clearly states what the tool does and its scope.

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 clearly indicates when to use the tool (to get orbital data for entire groups) and implies alternatives (get_satellite for single satellite). However, it does not explicitly state when not to use or list alternative tools.

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

All Celestrak toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

The tool set mixes several distinct domains (satellite orbital data, Pipeworx data routing, prediction-market analysis, memory management, subscriptions), but within the Pipeworx umbrella there is heavy overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying 5,756 tools. An agent could easily misselect between them, especially since ask_pipeworx and ask_pipeworx_beta are described as currently identical.

Naming Consistency3/5

Many tools follow a clear verb_noun pattern (list_subscriptions, create... none, but compare_entities, resolve_entity, generate_llms_txt, scan_dependency, subscribe/unsubscribe, remember/recall/forget), yet the naming is inconsistent across the set: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, get_satellite, get_group, recent_alerts, recent_changes, entity_profile, and deep_research do not share a uniform convention. CamelCase appears in polymarket_arbitrage, polymarket_edges, etc. while most others are snake_case, and the satellite tools (get_satellite, get_group, search_by_name) form a distinct sub-pattern that clashes with the Pipeworx meta-tools.

Tool Count2/5

34 tools is on the heavy side, and the effective surface is bloated: there are three variants of ask_pipeworx, four polymarket_* tools, three satellite-specific tools that are unrelated to the server's apparent core purpose, and several meta/utility tools (remember, recall, forget, pipeworx_feedback, pipeworx_trending, suggest_questions) that could be consolidated or are only tangentially related. The count itself is not extreme, but the scope is muddled: the server claims the name Celestrak (satellite tracking) while the overwhelming majority of tools are for Pipeworx data access and prediction markets, making the tool count feel inappropriate for either purpose.

Completeness3/5

For the Pipeworx data-access domain, the tool set is quite thorough: natural-language routing, grounded answers, deep research, entity profiling, entity comparison, claim verification, semantic search, and tool discovery are all present. However, there are notable gaps: the subscription lifecycle lacks an update/resume mechanism, and the satellite domain (the server's namesake) is severely incomplete — only three lookup tools with no live tracking, no group listing beyond a handful of groups, and no clear lifecycle CRUD. The memory tools (remember/recall/forget) are minimal but complete for their narrow scope.

Resources