Skip to main content
Glama
malkreide

wsl-envidat-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

WSL-Forschungseinheiten auflisten

wsl_list_organizations
Read-onlyIdempotent

List WSL research units with dataset counts to identify relevant organizations for querying Swiss environmental data.

Instructions

Listet alle WSL-Forschungseinheiten und deren Datensatz-Anzahl auf.

Gibt einen Überblick über die Forschungsgruppen der WSL, die Daten auf EnviDat publiziert haben. Nützlich zur Identifikation relevanter Organisationen für nachfolgende Abfragen mit wsl_get_organization.

Returns: CallToolResult: Lesbare Liste im Textkanal, dazu die Einheiten als structuredContent nach OrganizationListOutput.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalNoAnzahl Forschungseinheiten.
sourceNoDatenquelle dieses Resultats.EnviDat / WSL (envidat.ch)
licenseNoLizenzlage; die genaue Lizenz steht je Datensatz.various open licenses per dataset — see metadata
provenanceNoHerkunftsart: 'live_api' = direkt bei der Quelle abgefragt.live_api
retrieved_atNoAbrufzeitpunkt (UTC, ISO 8601).
organizationsNoDie Einheiten, nach Datensatzzahl absteigend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.3.1
    • addedOutput schema / $defs
      Added value: +{
+  "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_list_organizations`."
    • 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 / organizations
      Added value: +{
+  "description": "Die Einheiten, nach Datensatzzahl absteigend.",
+  "items": {
+    "$ref": "#/$defs/OrganizationSummary"
+  },
+  "title": "Organizations",
+  "type": "array"
+}
    • 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 / total
      Added value: +{
+  "default": 0,
+  "description": "Anzahl Forschungseinheiten.",
+  "title": "Total",
+  "type": "integer"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"wsl_list_organizationsOutput"New value: +"OrganizationListOutput"
  2. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds scope context (only groups with data on EnviDat) and explains the return shape: a readable text list plus structuredContent matching OrganizationListOutput. 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 and front-loaded with the core purpose. The second sentence adds practical context, and the Returns block is structured. It could be tightened slightly, but no sentence is wasted.

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 zero-parameter list tool with strong annotations and an output schema, the description is largely complete: it states what is listed, the scope, and the output format. Minor ambiguity remains about whether 'alle WSL-Forschungseinheiten' includes units with zero published datasets or only those with at least one, so it is not perfect.

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?

The tool has zero parameters and the schema coverage is 100%, so there are no parameter details to document. The baseline of 4 applies because nothing is missing and the description does not need to compensate for schema gaps.

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 ('Listet') and resource ('alle WSL-Forschungseinheiten'), and adds the dataset count per unit. It also distinguishes itself from the sibling wsl_get_organization by positioning this as the overview-level query that precedes a detailed organization lookup.

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 gives a clear usage context: it provides an overview of WSL research groups that published data on EnviDat and is useful for identifying relevant organizations before querying wsl_get_organization. It lacks an explicit when-not-to-use statement, but the intended workflow is evident.

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

Deploy Server

Other Tools