Space Launch & Starlink Tracker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LL2_BASE_URL | No | Base URL for The Space Devs Launch Library 2 API. Set to https://lldev.thespacedevs.com/2.3.0 for development. | https://thespacedevs.com/2.3.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upcoming_launchesB | Upcoming orbital launches worldwide from Launch Library 2 with live countdowns, provider, rocket, pad and status. Optional search (e.g. 'SpaceX', 'Falcon 9', 'Artemis', 'ISRO'). |
| next_launchA | Countdown and details for the very next launch, optionally filtered (e.g. 'Starship', 'Rocket Lab'). |
| starship_statusB | SpaceX Starship: next scheduled flights with countdowns, most recent flight outcomes, and latest news headlines. |
| satellite_passesA | Predict passes of the ISS (default), Tiangong, Hubble, or any satellite by name/NORAD id over a location, with naked-eye visibility (satellite sunlit, sky dark). Uses CelesTrak TLEs + SGP4. |
| starlink_passesA | Visible Starlink passes and 'trains' over a location. Default checks satellites from the 6 most recent Starlink launches (the bright, low trains); mode 'all' checks up to 3000 Starlinks over max 6 h. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct resource/action, but next_launch is essentially a filtered subset of upcoming_launches, and satellite_passes vs starlink_passes both compute location-based passes. The boundaries are still clear enough (specific object sets and train mode) that misselection risk is low.
All names are lowercase snake_case with a noun-oriented suffix, so the set reads consistently. The convention varies slightly (adjective_noun like upcoming_launches/next_launch vs subject_action like satellite_passes/starlink_passes), but this is a minor deviation.
Five tools sit at the low end of the well-scoped 3-15 range and each covers a meaningful capability. The set is slightly thin and next_launch partly duplicates upcoming_launches, keeping it just below ideal.
The tracker covers the core workflows: upcoming and imminent launches, Starship status, and satellite/Starlink passes. Gaps exist (no historical/archived launch lookup or generic satellite/object detail lookup), but these are minor and agents can work around them.