wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

WSL Walddaten & Forstinventar

wsl_get_forest_data

Read-onlyIdempotent

Fetch Swiss forest datasets from WSL/EnviDat, including inventory, health monitoring, and bark beetle data. Set limit and response format to refine results.

Instructions

Gibt Datensätze zum Schweizer Wald zurück, inkl. Landesforstinventar LFI.

Enthält u.a.:

Schweizerisches Landesforstinventar (LFI) – Waldzustand, Vorräte, Biodiversität
Sanasilva-Programm (Waldschadensmonitoring seit 1983)
Langzeitforschungsflächen LWF
Walddynamik und Waldentwicklung seit 1840
Borkenkäfer-Monitoring
Bodenlösung und Nährstoffhaushalt im Wald

Args: params (SimpleQueryInput): Anzahl Ergebnisse und Format

Returns: CallToolResult: Walddatensä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_forest_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 covered. The description adds context about the data sources (LFI, Sanasilva, LWF, etc.) and mentions the tool returns datasets, but it doesn't disclose details like pagination, response size limits, or that the limit parameter caps results. No contradiction with 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 reasonably concise, with a clear opening sentence followed by a bulleted list of data categories. The Args/Returns section is brief and front-loaded. The bullet list is useful but could be trimmed; overall it earns its place.

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?

The tool has an output schema and annotations covering safety, so the description doesn't need to explain return values. However, with 0% schema description coverage and only one parameter, the description could have explained the limit/format parameters more concretely. The data source list is helpful for an agent to decide if this tool matches a forest-related query, but usage guidance is thin.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only says 'Anzahl Ergebnisse und Format' (number of results and format) for the params argument. The schema itself documents limit and response_format with defaults, but the description adds minimal value beyond that. The nested SimpleQueryInput type is described as 'Für spezialisierte thematische Suchen' which is generic and doesn't explain forest-specific parameter behavior.

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 states the tool returns Swiss forest datasets including the national forest inventory (LFI), and lists specific data categories. It distinguishes itself from sibling tools like wsl_get_avalanche_data and wsl_get_naturgefahren_data by focusing on forest/Wald data, though it doesn't explicitly name a sibling.

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 description implies usage for forest-related queries by listing forest data topics, but it does not explicitly state when to use this tool versus alternatives like wsl_search or wsl_get_dataset. The context is clear enough for an agent to infer forest data queries, but no explicit when/when-not guidance is provided.

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

Deploy Server