wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

WSL Naturgefahren-Daten

wsl_get_naturgefahren_data

Read-onlyIdempotent

Fetch Swiss natural hazard datasets covering avalanches, landslides, rockfall, floods, and sediment transport to support risk assessments in spatial planning, school siting, and disaster protection.

Instructions

Gibt Datensätze zu Naturgefahren in der Schweiz zurück.

Enthält u.a.:

Tödliche Lawinenunfälle seit 1936/37
Murgang- und Rutschungsereignisse
Steinschlag- und Felssturzdaten
Schwemmkegel-Morphologie
Sedimenttransport in Gebirgsbächen
Hochwasserereignisse

Relevant für: Raumplanung, Schulhausstandort-Bewertungen, Katastrophenschutz, Klimafolgenabschätzung.

Args: params (SimpleQueryInput): Anzahl Ergebnisse und Format

Returns: CallToolResult: Naturgefahren-Datensätze der WSL

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`shown`	No	Davon in diesem Resultat enthalten.
`source`	No	Datenquelle dieses Resultats.	EnviDat / WSL (envidat.ch)
`license`	No	Lizenzlage; die genaue Lizenz steht je Datensatz.	various open licenses per dataset — see metadata
`datasets`	No	Die Treffer.
`provenance`	No	Herkunftsart: 'live_api' = direkt bei der Quelle abgefragt.	live_api
`total_found`	No	Gesamtzahl der Treffer in der Quelle.
`retrieved_at`	No	Abrufzeitpunkt (UTC, ISO 8601).
`suggested_tags`	No	ARCH-003: verwandte Tags bei leerem Resultat. Im Textkanal stehen sie seit jeher als Prosa; hier stehen sie als Liste.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.3.1Sep 22, 2026

addedOutput schema / $defs

Added value: +{
+  "DatasetSummary": {
+    "additionalProperties": false,
+    "description": "Ein Datensatz in Listenform — die neun Felder des bisherigen JSON.",
+    "properties": {
+      "license": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Lizenz dieses Datensatzes.",
+        "title": "License"
+      },
+      "modified": {
+        "default": "",
+        "description": "Letzte Aenderung (YYYY-MM-DD).",
+        "title": "Modified",
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Slug (URL-Name) des Datensatzes.",
+        "title": "Name"
+      },
+      "notes": {
+        "default": "",
+        "description": "Beschreibung, auf 300 Zeichen gekuerzt.",
+        "title": "Notes",
+        "type": "string"
+      },
+      "org": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Slug der Forschungseinheit.",
+        "title": "Org"
+      },
+      "resources": {
+        "default": 0,
+        "description": "Anzahl herunterladbarer Ressourcen.",
+        "title": "Resources",
+        "type": "integer"
+      },
+      "tags": {
+        "description": "Schlagwoerter.",
+        "items": {
+          "type": "string"
+        },
+        "title": "Tags",
+        "type": "array"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Titel des Datensatzes.",
+        "title": "Title"
+      },
+      "url": {
+        "default": "",
+        "description": "Permalink auf dem EnviDat-Portal.",
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "title": "DatasetSummary",
+    "type": "object"
+  }
+}

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

addedOutput schema / description

Added value: +"Resultat aller listenliefernden Such-Tools."

addedOutput schema / properties / datasets

Added value: +{
+  "description": "Die Treffer.",
+  "items": {
+    "$ref": "#/$defs/DatasetSummary"
+  },
+  "title": "Datasets",
+  "type": "array"
+}

addedOutput schema / properties / license

Added value: +{
+  "default": "various open licenses per dataset — see metadata",
+  "description": "Lizenzlage; die genaue Lizenz steht je Datensatz.",
+  "title": "License",
+  "type": "string"
+}

addedOutput schema / properties / provenance

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

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 / shown

Added value: +{
+  "default": 0,
+  "description": "Davon in diesem Resultat enthalten.",
+  "title": "Shown",
+  "type": "integer"
+}

addedOutput schema / properties / source

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

addedOutput schema / properties / suggested_tags

Added value: +{
+  "description": "ARCH-003: verwandte Tags bei leerem Resultat. Im Textkanal stehen sie seit jeher als Prosa; hier stehen sie als Liste.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Suggested Tags",
+  "type": "array"
+}

addedOutput schema / properties / total_found

Added value: +{
+  "default": 0,
+  "description": "Gesamtzahl der Treffer in der Quelle.",
+  "title": "Total Found",
+  "type": "integer"
+}

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

changedOutput schema / title

Previous value: -"wsl_get_naturgefahren_dataOutput"New value: +"SearchOutput"

First observedv0.2.0Jun 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful scope details such as 'Tödliche Lawinenunfälle seit 1936/37' and 'u.a.', but it doesn't describe operational behavior such as result limiting, pagination, or data source freshness. It does not contradict the annotations.

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

Conciseness4/5

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

The description is well structured: a one-line summary, a useful content list, applicability areas, then parameter and return sections. The Returns line is slightly redundant with the opening sentence, but overall the structure is efficient and scannable.

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

Completeness3/5

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

For a simple read-only query tool with one parameter and an output schema, the description covers purpose, content scope, and some use cases. It is incomplete in one important area: it does not clarify when to prefer this tool over the specialized wsl_get_avalanche_data or wsl_get_forest_data, leaving some ambiguity in tool selection.

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

Parameters3/5

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

The Args line 'params (SimpleQueryInput): Anzahl Ergebnisse und Format' correctly maps to the limit and response_format properties at a high level. However, it does not mention defaults, allowed response formats, or the max limit of 20, and schema description coverage is 0%. This is adequate but not comprehensive, especially since the nested schema description mentions unrelated themes like Wald and Dürre.

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

Purpose4/5

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

The description states a clear verb and resource: 'Gibt Datensätze zu Naturgefahren in der Schweiz zurück.' The bullet list makes the data scope concrete. It is distinguishable from most siblings, though it overlaps with wsl_get_avalanche_data because avalanche accidents are listed here too, so it doesn't fully differentiate itself from that sibling.

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

Usage Guidelines2/5

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

The description gives application contexts such as 'Raumplanung' and 'Katastrophenschutz', but it never says when to choose this tool instead of wsl_get_avalanche_data or wsl_get_forest_data. No exclusions or explicit alternatives are mentioned, which is a real gap given the avalanche overlap.

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

Deploy Server