Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TNS_BOT_IDNoOptional TNS bot ID for live TNS queries (create a bot at https://www.wis-tns.org/bots). Use together with TNS_BOT_NAME and TNS_API_KEY.
TNS_API_KEYNoOptional TNS bot API key for live TNS queries. Use together with TNS_BOT_ID and TNS_BOT_NAME. Never returned in responses, written to logs, or stored in the cache.
TNS_BOT_NAMENoOptional TNS bot name for live TNS queries. Use together with TNS_BOT_ID and TNS_API_KEY.
TNS_PUBLIC_CSVNoOptional path to a downloaded `tns_public_objects.csv.zip`, used for TNS answers when there are no bot credentials.
ASTROMCP_CACHE_DIRNoDisk cache directory for HTTP responses (minutes to hours), ExoFOP tables (12 h) and the TNS archive (20 h). Default is `~/.cache/astromcp`.~/.cache/astromcp

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
whats_hereA

Is it already known? Query TNS, SIMBAD, VSX, Gaia DR3, ExoFOP TOI/CTOI, ZTF (ALeRCE) and, if epoch (ISO UTC, e.g. '2026-10-20T03:15:00') is given, known asteroids (SkyBoT), all in parallel. Returns a verdict (the most specific of: 'known transient', 'known TESS object of interest', 'known variable', 'known asteroid', 'star', 'known ZTF alert source', 'known object', 'nothing known'), all matching labels, one-line evidence per hit, which sources failed, per-source details and image cutout links. ra/dec in decimal degrees (ICRS).

tns_objectA

Look up a Transient Name Server object by name, e.g. '2026agtq' or 'AT 2026agtq': position, type, redshift, discovery date/mag, reporting group, internal names.

tns_searchA

Transient Name Server cone search (live API if bot credentials are set, rate-limited to 10/min; otherwise the cached daily public archive).

ztf_lightcurveA

ZTF light curve from ALeRCE for an object id like 'ZTF26acatcla': per-band summary, detections (magpsf and magpsf_corr) and non-detection summary (last limit before first detection).

ztf_objects_nearC

ZTF objects (ALeRCE) within radius of a position.

rubin_objectA

Rubin/LSST object from the Fink broker by diaObjectId: position, light curve (AB mag from nJy flux), and cutout links of the latest alert.

rubin_recentA

Recent Rubin objects in a Fink LSST tag over the last N days (max 30), brightest first. Tags: most_likely_sn, sn_near_galaxy_candidate, extragalactic_new_candidate, extragalactic_lt20mag_candidate, hostless_candidate.

simbadB

SIMBAD objects within radius (nearest first): main id, object type, spectral type, redshift.

vsxB

AAVSO VSX variable stars within radius: name, variability type, range, period.

gaiaA

Gaia DR3 sources within radius, nearest first: G, BP-RP, parallax (+S/N), proper motion, RUWE, variability flag, and a 'likely_star' flag (parallax S/N > 3 or PM > 5 mas/yr).

tess_knownB

Known TESS objects for a TIC id and/or position: TOIs and CTOIs (ExoFOP-TESS) and TESS eclipsing binaries (Prsa et al. 2022). With only a TIC, its position comes from TIC v8.2.

asteroids_atB

Known solar-system objects near a position at a given time (IMCCE SkyBoT, geocentric): name, class, V mag, separation, motion. epoch_iso is UTC, e.g. '2026-10-20T03:15:00'.

cutout_urlsB

Image cutout links for a position: Legacy Survey DR10 (JPEG/FITS/viewer), Pan-STARRS color, DSS2 red and Aladin Lite.

observe_tonightA

What to observe tonight: recent (<= max_age_days), bright (TNS discovery mag <= mag_limit) transients that are still UNCLASSIFIED on TNS and observable from the site (lat/lon in degrees, east-positive longitude) during the night starting on the local evening of date (YYYY-MM-DD, default today UTC): above min_altitude while the Sun is below -12 deg and at least min_moon_sep from the Moon. Ranked by priority (brighter, younger, longer window). Use it to plan follow-up photometry or spectroscopic classification. Returns night window, Moon illumination and targets with max altitude, transit time, observing window and TNS link.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 14 tools

Disambiguation4/5

Most tools target a clearly distinct source+action pair (vsx, simbad, gaia, tess_known, asteroids_at, cutout_urls, observe_tonight), so misselection is unlikely for the bulk of the set. The main overlap is `whats_here`, which fans out to TNS, SIMBAD, VSX, Gaia, ExoFOP and ZTF in parallel and therefore duplicates the individual per-survey tools; descriptions hint at the verdict-vs-detail distinction but do not state a hard rule for when to use the aggregator versus the specialists.

Naming Consistency4/5

All names are lowercase snake_case with a predictable source-prefix convention: bare survey names for cone searches (vsx, simbad, gaia), `{survey}_{noun}` for targeted lookups (tns_object, ztf_lightcurve, rubin_recent, tess_known, asteroids_at), plus a few action-style names (whats_here, observe_tonight, cutout_urls). Verb-first naming is not universal, but the patterns are internally coherent and readable.

Tool Count5/5

14 tools sit comfortably in the well-scoped range for a multi-survey astronomy cross-match server. Each tool maps to a distinct data source or workflow step (transient lookup, stellar cross-match, solar-system check, cutouts, observing planner) rather than padding the surface.

Completeness4/5

The discovery-vetting lifecycle is well covered: cross-match known catalogues, pull light curves and alerts from ZTF and Rubin, get cutouts, and plan follow-up with observe_tonight. Minor gaps remain — SIMBAD/Gaia are cone-search only with no name-based object detail, TNS objects have no light-curve retrieval, and there is no target-specific visibility/ephemeris tool separate from the nightly planner, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues