erddap-mcp-demo
Server 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 |
|---|---|
| get_variable_standard_namesA | List all variable parameter CF standard names in datasets served by this ERDDAP server. These variable parameter standard names can be used when searching an ERDDAP for datasets containing variables measuring specific parameters. If we are looking for datasets with variables measuring a specific property, we should retrieve this list first and then use a discovered standard name value when searching the ERDDAP server. |
| search_datasetsC | List all datasets in an ERDDAP server |
| list_datasetsC | List all datasets in an ERDDAP server |
| list_dataset_variablesC | List all variables for a dataset in an ERDDAP server |
| get_dataset_variable_dataC | Get data for a variable in a dataset served by an ERDDAP server. Time is always included in the results. |
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
There is significant overlap: 'list_datasets' and 'search_datasets' have identical descriptions and appear to serve the same purpose, making it hard for an agent to distinguish them. Other tools are distinct but the duplication is a major issue.
Names follow a verb_noun pattern with underscores, but there is inconsistency in verb choice: 'list_datasets' vs 'search_datasets' for the same action, and 'get_' vs 'list_' across similar operations. While readable, the pattern is not fully consistent.
5 tools is within the well-scoped range for an ERDDAP server. However, the duplication reduces effective distinct tools to 4, making the count slightly less efficient but still acceptable.
The set covers listing datasets, listing variables, and retrieving data, but lacks tools for dataset metadata (e.g., attributes, time ranges) or data export formats. Basic querying is possible, but notable gaps exist.