wsl-envidat-mcp

Overview Schema Source Related Servers Discussions Admin

EnviDat Katalog-Übersicht

wsl_catalog_stats

Read-onlyIdempotent

Get a summary of the EnviDat catalog: domains, organizations, and dataset counts. Use it to see what data is available and how the catalog is structured.

Instructions

Gibt eine Übersicht über den EnviDat-Katalog zurück: Domänen, Organisationen, Datenmenge.

Nützlich als Einstiegspunkt: zeigt was im Katalog verfügbar ist, welche WSL-Forschungsdomänen besonders viele Datensätze haben, und wie der Katalog strukturiert ist.

Returns: CallToolResult: Lesbare Uebersicht im Textkanal, dazu die Zahlen als structuredContent nach CatalogStats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`portal`	No	URL des EnviDat-Portals.
`source`	No	Datenquelle dieses Resultats.	EnviDat / WSL (envidat.ch)
`domains`	No	Naeherungswerte je Domaene.
`license`	No	Lizenzlage; die genaue Lizenz steht je Datensatz.	various open licenses per dataset — see metadata
`provenance`	No	Herkunftsart: 'live_api' = direkt bei der Quelle abgefragt.	live_api
`retrieved_at`	No	Abrufzeitpunkt (UTC, ISO 8601).
`total_datasets`	No	Datensaetze im Katalog.
`top_organizations`	No	Die sechs groessten Einheiten.
`organization_count`	No	Anzahl Forschungseinheiten.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.3.1Sep 22, 2026

addedOutput schema / $defs

Added value: +{
+  "DomainCount": {
+    "additionalProperties": false,
+    "description": "Naeherungswert fuer eine Forschungsdomaene.",
+    "properties": {
+      "count": {
+        "default": 0,
+        "description": "Treffer der kuratierten Domaenen-Query.",
+        "title": "Count",
+        "type": "integer"
+      },
+      "domain": {
+        "description": "Schluessel der Domaene, z.B. 'wald'.",
+        "title": "Domain",
+        "type": "string"
+      },
+      "label": {
+        "description": "Anzeigename der Domaene.",
+        "title": "Label",
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "label"
+    ],
+    "title": "DomainCount",
+    "type": "object"
+  },
+  "OrganizationSummary": {
+    "additionalProperties": false,
+    "description": "Eine WSL-Forschungseinheit in Listenform.",
+    "properties": {
+      "description": {
+        "default": "",
+        "description": "Kurzbeschreibung.",
+        "title": "Description",
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Slug der Einheit.",
+        "title": "Name"
+      },
+      "package_count": {
+        "default": 0,
+        "description": "Anzahl publizierter Datensaetze.",
+        "title": "Package Count",
+        "type": "integer"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Ausgeschriebener Name.",
+        "title": "Title"
+      }
+    },
+    "title": "OrganizationSummary",
+    "type": "object"
+  }
+}

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

addedOutput schema / description

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

addedOutput schema / properties / domains

Added value: +{
+  "description": "Naeherungswerte je Domaene.",
+  "items": {
+    "$ref": "#/$defs/DomainCount"
+  },
+  "title": "Domains",
+  "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 / organization_count

Added value: +{
+  "default": 0,
+  "description": "Anzahl Forschungseinheiten.",
+  "title": "Organization Count",
+  "type": "integer"
+}

addedOutput schema / properties / portal

Added value: +{
+  "default": "",
+  "description": "URL des EnviDat-Portals.",
+  "title": "Portal",
+  "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 / source

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

addedOutput schema / properties / top_organizations

Added value: +{
+  "description": "Die sechs groessten Einheiten.",
+  "items": {
+    "$ref": "#/$defs/OrganizationSummary"
+  },
+  "title": "Top Organizations",
+  "type": "array"
+}

addedOutput schema / properties / total_datasets

Added value: +{
+  "default": 0,
+  "description": "Datensaetze im Katalog.",
+  "title": "Total Datasets",
+  "type": "integer"
+}

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

changedOutput schema / title

Previous value: -"wsl_catalog_statsOutput"New value: +"CatalogStats"

First observedv0.2.0Jun 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description only needs to add context. It does so by disclosing the return shape: a readable overview in the text channel plus numbers as structuredContent, which goes beyond what the annotations convey.

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 compact and front-loads the core purpose in the first sentence. There is slight redundancy between 'Übersicht' in the title and the opening line, but the added detail about domains, organizations, data volume, and the structuredContent return is purposeful.

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

Completeness5/5

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

For a parameterless, read-only catalog overview with an output schema and supporting annotations, the description provides everything an agent needs: what the tool does, when to use it, and what form the result takes. No critical information is missing.

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 zero parameters, the schema already fully documents the input surface; the baseline is 4. The description appropriately mentions what the output covers but does not need to add parameter-level 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 names a specific verb and resource ('Gibt eine Übersicht über den EnviDat-Katalog zurück') and spells out what the overview contains: domains, organizations, and data volume. It also frames the tool as an entry point, which distinguishes it from the sibling search/get/list tools.

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?

It clearly states the intended context: 'Nützlich als Einstiegspunkt' and describes what kind of orientation it provides. It does not explicitly name alternative tools or say when not to use it, but for a zero-parameter overview tool the usage guidance is sufficiently clear.

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

Deploy Server