Rasdaman MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RASDAMAN_URL | No | URL for the rasdaman server | http://localhost:8080/rasdaman/ows |
| RASDAMAN_PASSWORD | No | Sets the password for authentication | rasguest |
| RASDAMAN_USERNAME | No | Username for authentication | 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 |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_coveragesA | Lists all available datacubes (coverages) in rasdaman. |
| describe_coverageA | 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_queryA | Executes a Web Coverage Processing Service (WCPS) query in rasdaman. Use this for spatio-temporal subsetting of datacubes, processing, aggregation, filtering. Returns a structured dictionary indicating success, result_type, original query, the actual result value for scalar and small JSON or file path for large/binary results. Important: Show the actual WCPS query and the result file path to the user. |
| wcps_doc_chaptersA | Lists the detailed WCPS documentation chapters, one per topic, each with a description of what it covers and when to fetch it. Use when the crash course is not detailed enough — pick the chapter matching your problem and fetch it with wcps_get_chapter(name). After a failed query, the 'common-errors' chapter maps error symptoms to fixes. |
| wcps_get_chapterA | Returns one full WCPS documentation chapter (markdown) by name, as listed by wcps_doc_chapters(). Example: wcps_get_chapter("switch-case"). |
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 6 tools
Each tool maps to a distinct action: listing coverages, describing a coverage, learning WCPS basics, executing a query, listing doc chapters, and fetching a chapter. The documentation tools are explicitly tiered (crash course -> chapter index -> chapter body), so there is little risk of misselection.
The names are in readable snake_case, but they mix bare verb_noun names (list_coverages, describe_coverage, execute_wcps_query) with wcps_-prefixed resource-style names (wcps_query_crash_course, wcps_doc_chapters, wcps_get_chapter). The prefix and verb placement are inconsistent even though the overall style is still navigable.
Six tools is an appropriate size for a rasdaman querying server: coverage discovery, metadata inspection, query execution, and three levels of documentation. No tool feels redundant or missing at a high level.
The discover -> describe -> learn -> execute -> debug workflow is well covered. Minor gaps include a lack of write/ingest/update/delete operations for coverages and no explicit way to retrieve the contents of large result files, but these are likely outside the server's query-focused scope.