Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
starfetch_list_presetsA

List built-in TAP service presets before selecting an explicit target for metadata inspection.

starfetch_registry_searchA

Search VO registry metadata when no built-in preset fits; inspect the selected service before querying it.

starfetch_tap_availabilityA

Check whether the selected TAP service reports itself available; an unavailable service is not an empty catalog result.

starfetch_tap_capabilitiesA

Inspect the selected TAP service's languages, formats, and authentication requirements before using service-specific features.

starfetch_tap_tablesA

List tables on the selected TAP service before choosing an exact table for ADQL.

starfetch_tap_columnsA

Inspect names, datatypes, units, and descriptions for an exact metadata-discovered table before constructing ADQL.

starfetch_tap_queryA

Run a small bounded synchronous TAP ADQL query after inspecting the exact table and columns. Use TOP in ADQL and/or maxrec, and treat tool errors as failures rather than empty scientific results.

starfetch_tap_submit_jobA

Submit metadata-backed bounded ADQL as an explicit TAP async job when synchronous querying is insufficient. Preserve the exact query and use starfetch_tap_query for small work.

starfetch_tap_job_statusB

Read the current phase and links for a TAP async job.

starfetch_tap_job_waitA

Poll a TAP async job until completion, timeout, or terminal failure. This is an explicit wait and never starts a background job.

starfetch_tap_job_fetchA

Fetch a TAP async job result. JSON and JSONL conversion supports VOTable, CSV, and TSV rows.

starfetch_tap_job_deleteB

Delete a TAP async job from the remote service.

Prompts

Interactive templates invoked by user choice

NameDescription
query_astronomy_catalogPlan and execute a bounded metadata-first astronomy catalog query.
explore_serviceInspect a TAP service before constructing service-specific ADQL.
run_cone_searchBuild and run a bounded metadata-backed ADQL cone search.
troubleshoot_adqlDiagnose a failed ADQL query by returning to service metadata.

Resources

Contextual data attached and managed by the client

NameDescription
Starfetch workflow guideComplete metadata-first Starfetch workflow, fallback, safety, and reporting guidance.
Starfetch ADQL guideMetadata-backed ADQL syntax and failure recovery guidance.
Starfetch TAP metadata guideWorkflow for inspecting TAP availability, capabilities, tables, and columns.
Starfetch query safety guideBounds, untrusted-content handling, and reproducible reporting for public TAP queries.
Starfetch Gaia service guideGaia-specific query guidance and interpretation limits.
Starfetch SIMBAD service guideSIMBAD-specific query guidance and interpretation limits.
Starfetch VizieR service guideVizieR catalog discovery, schema inspection, and bounded-query guidance.
Starfetch NASA Exoplanet Archive service guideNASA Exoplanet Archive table-selection and scientific-interpretation guidance.
Starfetch IRSA service guideIRSA catalog selection, metadata, and bounded-query guidance.
Starfetch cone-search exampleMetadata-first bounded cone-search workflow using discovered coordinate columns.
Starfetch proper-motion exampleComplete metadata-first Gaia proper-motion workflow.
Starfetch exoplanet exampleMetadata-first short-period exoplanet query workflow.
Starfetch SIMBAD object-types exampleMetadata-first SIMBAD regional object-type query workflow.

TDQS

A3.9/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct TAP workflow step—service discovery, metadata inspection, synchronous query, or async job lifecycle—and the descriptions clearly separate near-neighbors like availability vs capabilities and query vs submit_job. No two tools appear interchangeable.

Naming Consistency3/5

All tools share a consistent starfetch_ prefix and snake_case style, but the suffix pattern is mixed: list_presets and submit_job use verb-noun order, registry_search and job_wait/fetch/delete use noun-verb order, and availability/capabilities/tables/columns are bare nouns. The grouping is readable, but verb placement is not uniform.

Tool Count5/5

Twelve tools is well-scoped for a TAP client; each tool covers a necessary step from service discovery and metadata inspection through synchronous queries and async job cleanup. There is no obvious redundancy.

Completeness4/5

The tool set covers the main TAP workflow comprehensively: discovery, capabilities, tables, columns, synchronous queries, and async job lifecycle. Minor gaps such as missing explicit job abort/cancel or job listing exist, but agents can work around them using wait and delete.

Maintenance

ActivityMaintained
ResponsivenessNo issues