Rasdaman MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RASDAMAN_URL | No | URL for the rasdaman server. Can be set via environment variable or command-line argument --rasdaman-url (default: http://localhost:8080/rasdaman/ows). | |
| RASDAMAN_PASSWORD | No | Password for authentication. Can be set via environment variable or command-line argument --password (default: rasguest). | |
| RASDAMAN_USERNAME | No | Username for authentication. Can be set via environment variable or command-line argument --username (default: rasguest). |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_coveragesA | Lists all available datacubes (coverages) in rasdaman. |
| describe_coverageC | Retrieves structural metadata for a specific datacube (coverage). |
| wcps_query_crash_courseA | Returns a crash course on writing WCPS queries: learn the basic syntax, common operations, and best practices for WCPS queries. It's recommended to check this before executing queries. |
| execute_wcps_queryB | Executes a Web Coverage Processing Service (WCPS) query in rasdaman. Use this for spatio-temporal subsetting of datacubes, processing, aggregation, or filtering. If the query returns binary data (e.g., an image or NetCDF file), the tool saves it to a temporary file and return the path. Important: Show the actual WCPS query and the result file path to the user. |
| validate_wcps_queryA | Use this to check if your WCPS query is syntactically correct before execution. Returns "VALID" if the query syntax is correct, or "INVALID SYNTAX: " otherwise. |
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
Each tool has a clearly distinct purpose: listing coverages, describing a coverage, validating queries, executing queries, and a crash course. There is no overlap in functionality.
Most tools follow a verb_noun pattern with snake_case (e.g., describe_coverage, list_coverages). The exception is 'wcps_query_crash_course', which is a noun phrase, but it remains consistent in using underscores.
With 5 tools, the server covers the essential operations for a datacube query service: exploration, validation, execution, and learning. The count is well-scoped for its purpose.
The tool set covers the key workflows for WCPS querying: list, describe, validate, and execute. Minor gaps exist, such as missing tools for managing coverages or retrieving example queries, but the core functionality is complete.