wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

EnviDat Suche

wsl_search

Read-onlyIdempotent

Search Swiss environmental research data from WSL/EnviDat by combining keywords, curated domains, organizations, and geographic bounds. Find forest, snow, avalanche, and biodiversity datasets.

Instructions

Unifizierte Suche im EnviDat-Katalog der WSL (Eidg. Forschungsanstalt für Wald, Schnee und Landschaft). Kombiniert frei wählbar Stichwort, kuratierte Forschungsdomäne, Organisation und Bounding-Box.

Schweizer Umweltforschung, Schulhaus-Umgebungsanalysen, Klimafolgen-Recherche, kantonale Umweltberichte, Lawinendaten, Waldzustand, Biodiversität, Naturgefahren.

Mindestens einer der Filter (query/domain/organization/bbox) muss gesetzt sein. Solr-Syntax ist möglich, 'OR' ist aber Stopwort. Bei leerem Resultat liefert das Tool verwandte Tags als Vorschlag.

query='snow avalanche' → SLF-Lawinendaten. domain='wald' → kuratierte LFI-/Sanasilva-Suche. bbox=[8.35,47.15,8.98,47.72] → Kanton Zürich. query='forest', organization='wsl' → WSL-Walddatensätze.

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

First observedv0.2.0Jun 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description supplements the readOnly/idempotent annotations with practical behavioral details: at least one filter must be set, Solr syntax is supported but 'OR' is a stopword, filters combine as AND, and an empty result returns related tag suggestions. These details go beyond the annotations and help the agent predict system behavior.

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 use_case, important_notes, and example sections, front-loading the core purpose before the details. It is longer than minimal but each section adds useful operational guidance rather than filler.

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 search tool with several filters, the description covers the key constraints, gives illustrative examples, and explains the empty-result behavior. It does not describe output format or pagination, but annotations and the output schema cover some of that, and an output schema is present, so the description is sufficiently complete for invocation.

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?

Schema description coverage is reported as 0%, so the description must compensate, and it partially does: it explains the query/domain/organization/bbox combination and gives concrete examples for each main filter. However, it does not add much meaning for limit, offset, or response_format, and relies on the nested schema's descriptions for those details.

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 action and resource: unified search over the EnviDat catalog of the WSL. It names the combinable filters (keyword, curated research domain, organization, bounding box), which clearly distinguishes it from sibling tools like wsl_get_dataset, wsl_list_organizations, or wsl_get_avalanche_data.

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 provides concrete use cases (e.g., climate-impact research, avalanche data, forest condition) and example queries for different filters. It does not explicitly name alternative tools or exclusion conditions, but the context makes it clear this is the search entry point, so usage is strongly implied.

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

Deploy Server