wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

SLF Lawinen- & Schneedaten

wsl_get_avalanche_data

Read-onlyIdempotent

Retrieve Swiss avalanche and snow datasets from WSL/SLF, including fatal avalanche accidents since 1936/37, long-term snow measurements, and high-alpine meteorological records.

Instructions

Lawinen- und Schneedaten vom WSL-Institut fuer Schnee- und Lawinenforschung (SLF).

Enthält u.a.:

Tödliche Lawinenunfälle in der Schweiz seit 1936/37
Langjährige Schneemessreihen (Station Stillberg Davos, 2090 m)
Meteorologische Langzeitdaten Hochgebirge
Schneephysik-Forschungsdaten

Args: params (SimpleQueryInput): Anzahl Ergebnisse und Format

Returns: CallToolResult: Lawinen- und Schneedatensätze des SLF

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_avalanche_dataOutput"New value: +"SearchOutput"

First observedv0.2.0Jun 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description carries a lighter burden. It adds dataset content scope and the return type, but does not disclose details like pagination, output formatting behavior, or how limit affects results beyond what schema defaults imply.

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 with a front-loaded domain statement, a compact bullet list, and clearly labeled Args and Returns sections. There is slight redundancy between the opening line and the Returns line, but no wasted or misleading content.

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

Completeness4/5

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

For a one-argument, read-only tool with strong annotations and an output schema, the description is largely complete: it names the data source, lists contents, and explains the parameter. The main remaining gap is explicit cross-tool usage differentiation, which is left to inference from sibling names and domain terms.

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?

Schema property descriptions are effectively absent, and the Args line compensates by explaining the nested params as 'Anzahl Ergebnisse und Format', which directly maps to limit and response_format. The schema then supplies constraints, defaults, and enum values, so the description provides the missing semantic layer.

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 clearly identifies the resource as SLF avalanche and snow data and lists concrete dataset categories, which helps distinguish it from forest and natural-hazard siblings. It lacks an explicit action verb like 'retrieve' or 'search', but the tool name and returns section establish the operation.

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

Usage Guidelines3/5

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

The scope is implied by the title and content bullets: use this for avalanche and snow data. However, there is no explicit when-to-use guidance, and no alternatives such as wsl_get_forest_data or wsl_get_naturgefahren_data are named or excluded.

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

Deploy Server