wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

EnviDat Datensatz-Details

wsl_get_dataset

Read-onlyIdempotent

Retrieve complete metadata and download URLs for an EnviDat dataset by its ID or slug, including DOI, license, authors, and spatial extent. Get details after a search to access public and non-public resources.

Instructions

Gibt vollständige Metadaten und Ressourcen (Download-URLs) eines EnviDat-Datensatzes zurück.

Detail-Ansicht eines konkreten Datensatzes mit DOI, Lizenz, Autoren, Download-Links und räumlicher Ausdehnung. Folge-Schritt nach wsl_search.

id_or_slug ist entweder die UUID oder der URL-Slug aus dem Suchergebnis (Feld 'name'). Liefert auch nicht-öffentliche Resource-Metadaten wenn vorhanden.

id_or_slug='fatal-avalanche-accidents-in-switzerland-since-1936-37' → vollständige Lawinen-Datenbankbeschreibung mit CSV-Download-Link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`doi`	No	DOI ohne Praefix, wenn vergeben.
`org`	No	Titel der Forschungseinheit.
`url`	No	Permalink auf dem EnviDat-Portal.
`name`	No	Slug (URL-Name).
`tags`	No	Schlagwoerter.
`notes`	No	Vollstaendige Beschreibung.
`title`	No	Titel.
`source`	No	Datenquelle dieses Resultats.	EnviDat / WSL (envidat.ch)
`authors`	No	Autorenangabe der Quelle.
`created`	No	Erstellt (YYYY-MM-DD).
`license`	No	Lizenz.
`spatial`	No	Raeumliche Ausdehnung, GeoJSON als String wie von der Quelle geliefert.
`modified`	No	Letzte Aenderung (YYYY-MM-DD).
`resources`	No	Herunterladbare Dateien.
`provenance`	No	Herkunftsart: 'live_api' = direkt bei der Quelle abgefragt.	live_api
`retrieved_at`	No	Abrufzeitpunkt (UTC, ISO 8601).
`publication_year`	No	Publikationsjahr.

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv0.3.1Sep 22, 2026

addedOutput schema / $defs

Added value: +{
+  "ResourceEntry": {
+    "additionalProperties": false,
+    "description": "Eine herunterladbare Datei eines Datensatzes.",
+    "properties": {
+      "description": {
+        "default": "",
+        "description": "Beschreibung der Datei.",
+        "title": "Description",
+        "type": "string"
+      },
+      "format": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Format, z.B. CSV, NetCDF.",
+        "title": "Format"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Dateiname oder Bezeichnung.",
+        "title": "Name"
+      },
+      "size": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Groesse in Bytes, wenn bekannt.",
+        "title": "Size"
+      },
+      "url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Direkter Download-Link.",
+        "title": "Url"
+      }
+    },
+    "title": "ResourceEntry",
+    "type": "object"
+  }
+}

addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / description

Added value: +"Die kuratierten Detailfelder eines Datensatzes.\n\nBewusst NICHT das rohe CKAN-Paket: Dessen 42 Felder haben kein stabiles\nSchema, und ein `outputSchema` darueber waere wieder eine Zusage, die\nniemand halten kann. Wer alle Rohfelder braucht, bekommt sie unveraendert\nueber `response_format=\"json\"` im Textkanal — dieser Weg wird hier nicht\nangetastet, damit niemand Daten verliert, die er heute schon abholt."

addedOutput schema / properties / authors

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Autorenangabe der Quelle.",
+  "title": "Authors"
+}

addedOutput schema / properties / created

Added value: +{
+  "default": "",
+  "description": "Erstellt (YYYY-MM-DD).",
+  "title": "Created",
+  "type": "string"
+}

addedOutput schema / properties / doi

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "DOI ohne Praefix, wenn vergeben.",
+  "title": "Doi"
+}

addedOutput schema / properties / license

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Lizenz.",
+  "title": "License"
+}

addedOutput schema / properties / modified

Added value: +{
+  "default": "",
+  "description": "Letzte Aenderung (YYYY-MM-DD).",
+  "title": "Modified",
+  "type": "string"
+}

addedOutput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Slug (URL-Name).",
+  "title": "Name"
+}

addedOutput schema / properties / notes

Added value: +{
+  "default": "",
+  "description": "Vollstaendige Beschreibung.",
+  "title": "Notes",
+  "type": "string"
+}

addedOutput schema / properties / org

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Titel der Forschungseinheit.",
+  "title": "Org"
+}

addedOutput schema / properties / provenance

Added value: +{
+  "default": "live_api",
+  "description": "Herkunftsart: 'live_api' = direkt bei der Quelle abgefragt.",
+  "title": "Provenance",
+  "type": "string"
+}

addedOutput schema / properties / publication_year

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Publikationsjahr.",
+  "title": "Publication Year"
+}

addedOutput schema / properties / resources

Added value: +{
+  "description": "Herunterladbare Dateien.",
+  "items": {
+    "$ref": "#/$defs/ResourceEntry"
+  },
+  "title": "Resources",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / retrieved_at

Added value: +{
+  "description": "Abrufzeitpunkt (UTC, ISO 8601).",
+  "title": "Retrieved At",
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "default": "EnviDat / WSL (envidat.ch)",
+  "description": "Datenquelle dieses Resultats.",
+  "title": "Source",
+  "type": "string"
+}

addedOutput schema / properties / spatial

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Raeumliche Ausdehnung, GeoJSON als String wie von der Quelle geliefert.",
+  "title": "Spatial"
+}

addedOutput schema / properties / tags

Added value: +{
+  "description": "Schlagwoerter.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Tags",
+  "type": "array"
+}

addedOutput schema / properties / title

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Titel.",
+  "title": "Title"
+}

addedOutput schema / properties / url

Added value: +{
+  "default": "",
+  "description": "Permalink auf dem EnviDat-Portal.",
+  "title": "Url",
+  "type": "string"
+}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"wsl_get_datasetOutput"New value: +"DatasetDetail"

First observedv0.2.0Jun 4, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is already known. The description adds meaningful behavioral context beyond that: it returns download URLs, can include non-public resource metadata when present, and lists the metadata fields such as DOI, license, authors, and spatial extent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and structured with clear use_case, important_notes, and example sections. Every section earns its place and adds actionable guidance rather than repeating the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description covers everything an agent needs to invoke the tool: input provenance, supported identifier forms, a concrete example, and a summary of returned metadata and resources. No critical calling information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the context signal reports 0% schema coverage, the embedded schema already provides descriptions and examples for both parameters. The description adds extra semantic value by explaining that id_or_slug can be a UUID or URL slug from the search result's 'name' field, and the example clarifies exactly what kind of input is expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns complete metadata and resources (download URLs) of an EnviDat dataset. The use_case explicitly distinguishes it as the detail view of a concrete dataset and positions it as the follow-up to wsl_search, so it is not confused with list/search siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states when to use the tool: as the detail view after wsl_search, with id_or_slug taken from the search result field 'name'. It does not explicitly name excluded alternatives, but the use_case and sibling context make the selection boundary clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server