spedas-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spedas_overviewA | Describe available SPEDAS MCP capabilities and the recommended workflow. |
| search_spedas_data_sourcesC | Recommend whether a SPEDAS request should start with CDAWeb, PDS, SPICE, or a mix. |
| plan_spedas_observationB | Plan a SPEDAS science workflow before using low-level CDAWeb/PDS/SPICE tools. |
| compare_cdaweb_pds_spiceC | Compare CDAWeb, PDS, and SPICE roles for a SPEDAS MCP science request. |
| create_spedas_analysis_bundleC | Create a lightweight request/provenance bundle for a planned SPEDAS analysis. |
| browse_observatoriesA | List CDAWeb observatories with descriptions, dataset counts, and instruments. |
| load_observatoryB | Load CDAWeb observatory prompt/catalog for a lowercase observatory stem. |
| browse_parametersC | Browse variables/metadata for one or more CDAWeb dataset IDs. |
| fetch_dataC | Fetch CDAWeb timeseries data, write a file, and return metadata/stats only. |
| browse_pds_missionsB | List PDS PPI missions/spacecraft with descriptions, dataset counts, and instruments. |
| load_pds_missionA | Load PDS PPI mission prompt/catalog for a lowercase mission stem. |
| browse_pds_parametersC | Browse variables/metadata for one or more PDS PPI dataset IDs. |
| fetch_pds_dataC | Fetch PDS PPI timeseries data, write a file, and return metadata/stats only. |
| list_spice_missionsA | List supported SPICE spacecraft/body missions with NAIF IDs and kernel status. |
| get_ephemerisC | Get single-time state inline or timeseries trajectory written to CSV. |
| compute_distanceC | Compute distance between two SPICE targets over a time range. |
| transform_coordinatesC | Transform a 3D vector between SPICE coordinate frames. |
| list_coordinate_framesA | List supported SPICE coordinate frames and usage notes. |
| manage_cdaweb_cacheC | Manage CDAWeb cache and metadata/catalog refresh operations. |
| manage_pds_cacheC | Manage PDS cache and metadata/catalog refresh operations. |
| manage_spice_kernelsC | Manage SPICE kernels and cache state. |
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 21 tools
Each tool has a clearly distinct purpose, with separate tools for browsing, fetching, managing caches, SPICE operations, and high-level planning. There is no ambiguity between tools like browse_observatories and browse_pds_missions, as they target different data sources.
All tool names follow a consistent verb_noun pattern using underscores (e.g., browse_observatories, fetch_data, manage_spice_kernels). High-level tools consistently include 'spedas' as a prefix. The naming is predictable and easy to navigate.
With 21 tools, the set is slightly above the ideal range of 3-15, but the number is justified by the need to cover three distinct data sources (CDAWeb, PDS, SPICE) plus planning and management operations. The tools are well-scoped and not excessive.
The tool set covers core workflows: browsing, data fetching, cache management, SPICE computations, and planning. Minor gaps exist, such as the lack of a search tool for datasets by criteria, but overall it supports the main use cases for space physics data analysis.