wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

WSL-Forschungseinheit Details

wsl_get_organization

Read-onlyIdempotent

Retrieve details of a WSL research unit, including its description, contact, and dataset overview. Specify an organization slug like 'slf' to get the unit's data.

Instructions

Gibt Details einer WSL-Forschungseinheit inklusive ihrer Datensätze zurück.

Liefert Beschreibung, Kontakt und Datensatz-Übersicht einer Organisation. Das SLF (Institut für Schnee- und Lawinenforschung) ist als 'slf' abrufbar.

Args: params (GetOrganizationInput): Mit: - name (str): Organisations-Slug (z.B. 'wsl', 'slf') - include_datasets (bool): Datensätze mitausgeben

Returns: CallToolResult: Lesbare Details im Textkanal, dazu die Einheit als structuredContent nach OrganizationDetail.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Slug der Einheit.
`title`	No	Ausgeschriebener Name.
`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	Datensaetze der Einheit. Der Textkanal zeigt hoechstens zehn; hier steht, was die Quelle geliefert hat.
`provenance`	No	Herkunftsart: 'live_api' = direkt bei der Quelle abgefragt.	live_api
`description`	No	Beschreibung.
`retrieved_at`	No	Abrufzeitpunkt (UTC, ISO 8601).
`package_count`	No	Anzahl Datensaetze insgesamt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.3.1Sep 22, 2026

addedOutput schema / $defs

Added value: +{
+  "DatasetRef": {
+    "additionalProperties": false,
+    "description": "Ein Datensatz-Verweis innerhalb einer Organisation.",
+    "properties": {
+      "modified": {
+        "default": "",
+        "description": "Letzte Aenderung (YYYY-MM-DD).",
+        "title": "Modified",
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Slug.",
+        "title": "Name"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Titel.",
+        "title": "Title"
+      },
+      "url": {
+        "default": "",
+        "description": "Permalink.",
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "title": "DatasetRef",
+    "type": "object"
+  }
+}

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

addedOutput schema / description

Added value: +"Resultat von `wsl_get_organization`."

addedOutput schema / properties / datasets

Added value: +{
+  "description": "Datensaetze der Einheit. Der Textkanal zeigt hoechstens zehn; hier steht, was die Quelle geliefert hat.",
+  "items": {
+    "$ref": "#/$defs/DatasetRef"
+  },
+  "title": "Datasets",
+  "type": "array"
+}

addedOutput schema / properties / description

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

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

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Slug der Einheit.",
+  "title": "Name"
+}

addedOutput schema / properties / package_count

Added value: +{
+  "default": 0,
+  "description": "Anzahl Datensaetze insgesamt.",
+  "title": "Package Count",
+  "type": "integer"
+}

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

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

addedOutput schema / properties / title

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

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

changedOutput schema / title

Previous value: -"wsl_get_organizationOutput"New value: +"OrganizationDetail"

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?

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context by explaining that the result is delivered both as readable text and as structuredContent conforming to OrganizationDetail, which goes beyond 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 into purpose, Args, and Returns sections, making it easy to scan. There is slight redundancy between the first and second sentences, both stating that datasets are included, but overall every section earns its place.

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 simple tool with one required parameter, existing output schema, and strong annotations covering safety, the description is nearly complete: it explains parameters, return format, and gives a real-world slug example. The only notable gap is explicit guidance on when to choose this tool over sibling list/search tools.

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?

With schema description coverage reported at 0%, the description compensates by explaining both parameters: name is an organization slug with 'wsl/slf examples, and include_datasets controls whether datasets are included. It does not mention the default value for include_datasets, but the schema provides that detail.

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 uses a specific verb and resource: 'Gibt Details einer WSL-Forschungseinheit inklusive ihrer Datensätze zurück' and names the fields returned (Beschreibung, Kontakt, Datensatz-Übersicht). It also distinguishes itself from siblings like wsl_list_organizations and wsl_get_dataset by focusing on a single organization's details, including its datasets.

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 makes it clear that this tool is for retrieving details of a specific known organization by slug, with 'slf' as a concrete example. However, it does not explicitly say when to choose this tool instead of alternatives, nor does it mention discovery workflows such as using wsl_list_organizations to find valid slugs.

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

Deploy Server