GDI Catalogue MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CSW_URL | No | URL of the CSW catalog to use. Standard: https://gdk.gdi-de.org/gdi-de/srv/ger/csw. For a different CSW catalog set CSW_URL in the process environment. The URL is configured exclusively by the operator, not offered as a tool parameter. Other catalogs are not tested; CSW 2.0.2 and Dublin Core output must be supported. | https://gdk.gdi-de.org/gdi-de/srv/ger/csw |
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 |
|---|---|
| search_recordsA | Search CSW metadata with words (e.g. 'Lärm Ingolstadt'), not raw CQL. limit 1–50, start is 1-based. Use next_record to paginate; zero means end. Call get_record for metadata and links. |
| get_recordA | Retrieve a record's Dublin Core metadata, resource links and metadata bounding boxes by its exact returned ID. Links are not verified/downloaded; a footprint does not prove local data coverage. |
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 2 tools
search_records is for discovery via keywords and pagination, while get_record retrieves a specific record by its exact ID. The two purposes are clearly separated with no overlap, so an agent can easily choose the correct tool.
Both tools follow a consistent snake_case verb_noun pattern: search_records and get_record. The plural/singular noun difference reflects the operation (search many vs. get one) and does not break the pattern.
With only two tools, the surface feels thin for a CSW catalogue even though the two provided operations are focused. The count is borderline per the rubric for 1–2 tools, lacking additional conveniences like capabilities or spatial search.
The core read-only lifecycle of discovery (search) and retrieval by ID (get_record) is fully covered, including pagination hints. Minor gaps remain, such as no direct spatial/bbox search or get_capabilities operation, but agents can work around these using keyword search.