telescopius-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELESCOPIUS_API_KEY | Yes | Your Telescopius API key (found under Telescopius → Settings → API Keys). | |
| TELESCOPIUS_ENV_FILE | No | Path to the .env file to read configuration from (overrides the default .env beside the project). | |
| TELESCOPIUS_FOCAL_MM | No | Default rig focal length in millimeters. | |
| TELESCOPIUS_SENSOR_MM | No | Default rig sensor size in millimeters. | |
| TELESCOPIUS_SENSOR_PX | No | Default rig sensor size in pixels. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sky_timesB | Rise/transit/set for the Sun, Moon and planets, plus every twilight time (astronomical darkness = sun.twilights.darkest_sunset .. darkest_sunrise). date: "YYYY-MM-DD" or "YYYY-MM-DD HH:mm:ss"; default now. Location defaults to home. |
| tonight_highlightsA | Telescopius' curated popular targets that are well placed on the given night. types: comma list, e.g. DEEP_SKY_OBJECT, GXY, COMET, ASTEROID. min_alt: degrees the target must reach; min_alt_minutes: time it must spend above that. moon_dist_min: minimum Moon separation in degrees at transit (string, the API also accepts its moon-avoidance presets). Each result carries tonight's imaging windows with moon illumination and distance. raw=True returns the untrimmed payload. |
| search_targetsA | Advanced target search across Telescopius' full catalogue. name: fuzzy name match (forces name-score ordering). size_*_arcmin: apparent size bounds in arcminutes. con: IAU constellation abbreviations, comma separated. cat: catalogue acronyms (e.g. M, NGC, IC, SH2). az_quadrants: NE,NW,SW,SE in view. hour_min/hour_max: session window as a decimal hour or a twilight keyword such as "astronomical_sunset" / "astronomical_sunrise". order: name, con, dec, mag, ra, rise, set, transit, size, subr, type, imaging_time, popularity, opposition. order_asc: default picks the useful direction: most popular first, and the longest imaging time / largest size first (popularity is a rank, so ascending = most popular). results: 1-120 per page. extra: any other API parameter passed through verbatim (e.g. {"subr_max": 22, "dec_min": 20}). raw=True returns the untrimmed payload. |
| target_infoB | One named target (e.g. "IC 1805", "Heart Nebula") with tonight's visibility windows. ephemeris: "daily" (positions through the night) or "yearly" (next 12 months). Falls back to a fuzzy match when the exact name finds nothing. |
| show_framingA | Frame a target in Telescopius' Telescope Simulator with the configured rig, in a visible browser window on this machine, and return a screenshot of the framing. target: object name (resolved via the API, e.g. "IC 1805", "Heart Nebula"); with ra_h/dec_deg given, it is only a label. mosaic: "COLSxROWS", e.g. "2x2". rotation: camera angle in degrees. focal_mm / sensor_mm ("11.136x6.264") / sensor_px ("3840x2160") override the default rig for this call. The window stays open for hands-on adjustment; close_framing closes it. |
| close_framingA | Close the framing browser window opened by show_framing. |
| my_observing_listsA | The account's saved observing lists (id, name, target count). |
| observing_listC | One observing list's targets with visibility for the given night. |
| weather_forecastB | Astronomy forecast: per night cloud cover, seeing, transparency, humidity, wind, temperature, dew risk and moon illumination (seeing/transparency are 0-100 scores). hourly_nights: also return the dark hours of the first N nights (0 = summary only). Nightly temperature is in °C: the API ignores temp_unit for the daily stats. Hourly rows carry no temperature or dew point, because the API returned different values for the same hour on repeated calls. Use relative_humidity and dew_risk instead. |
| astro_eventsB | Astronomical calendar (conjunctions, occultations, moon phases, showers...) for
the next |
| event_highlightsB | The most notable upcoming sky events (1-50), with local visibility flags. |
| my_equipmentB | Telescopes, cameras and other gear saved in the Telescopius account. |
| astro_newsB | Latest headlines from Telescopius' astronomy news feeds. |
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 13 tools
Most tools target clearly distinct resources and actions (sky_times, weather_forecast, target_info, show_framing/close_framing), and the two-list pattern (my_observing_lists vs observing_list) is well differentiated. The main ambiguity is between astro_events (full computed calendar) and event_highlights (curated upcoming events with visibility flags), which an agent could easily conflate, and tonight_highlights vs search_targets partially overlap in purpose.
All names are clean snake_case with a coherent convention (my_ prefix for account resources, noun-phrase domain names, verb_noun for actions). The only deviation is that a few tools are verb-first (search_targets, show_framing, close_framing) while most are noun phrases, which is minor and still readable.
13 tools is well within the ideal range and each earns its place across distinct functional areas: time, targets, framing, events, weather, lists, equipment, and news. No redundancy or bloat.
The surface covers the observing workflow well: sky timing, target discovery/inspection, framing, events, weather, saved lists, gear, and news. The notable gap is that the observing-list tools are read-only (no way to add, remove, or create lists/targets), and equipment/news are read-only, but these are minor for a largely informational server.