Skip to main content
Glama
malkreide

Zurich Open Data MCP Server

by malkreide
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

zurich_get_dataset

Read-onlyIdempotent

Retrieve complete metadata and resources for a Zurich Open Data dataset, including title, author, license, update interval, file formats, and download URLs.

Instructions

Ruft vollständige Metadaten und Ressourcen eines Datensatzes ab.

Gibt Titel, Beschreibung, Autor, Lizenz, Aktualisierungsintervall, alle verfügbaren Dateiformate und Download-URLs zurück.

Returns: Strukturiertes GetDatasetResult (JSON mit Ressourcen-IDs zum Verketten mit zurich_datastore_query) plus lesbares Markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
extrasNo
datasetNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv0.5.0
    • addedOutput schema / $defs
      Added value: +{
+  "DatasetSummary": {
+    "description": "Compact, machine-readable view of a CKAN dataset.",
+    "properties": {
+      "author": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Author"
+      },
+      "groups": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Groups",
+        "type": "array"
+      },
+      "id": {
+        "description": "CKAN dataset name/slug — use as dataset_id in zurich_get_dataset",
+        "title": "Id",
+        "type": "string"
+      },
+      "license": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "License"
+      },
+      "modified": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Last modified date (YYYY-MM-DD)",
+        "title": "Modified"
+      },
+      "notes": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Notes"
+      },
+      "num_resources": {
+        "default": 0,
+        "title": "Num Resources",
+        "type": "integer"
+      },
+      "resources": {
+        "items": {
+          "$ref": "#/$defs/ResourceInfo"
+        },
+        "title": "Resources",
+        "type": "array"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Tags",
+        "type": "array"
+      },
+      "title": {
+        "title": "Title",
+        "type": "string"
+      },
+      "update_interval": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Update Interval",
+        "type": "array"
+      },
+      "url": {
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "url"
+    ],
+    "title": "DatasetSummary",
+    "type": "object"
+  },
+  "ResourceInfo": {
+    "description": "A single downloadable resource of a dataset.",
+    "properties": {
+      "datastore_active": {
+        "default": false,
+        "description": "True if the resource is queryable via the CKAN DataStore API",
+        "title": "Datastore Active",
+        "type": "boolean"
+      },
+      "format": {
+        "title": "Format",
+        "type": "string"
+      },
+      "id": {
+        "description": "Resource UUID — use as resource_id for DataStore queries",
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Url"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "format"
+    ],
+    "title": "ResourceInfo",
+    "type": "object"
+  }
+}
    • addedOutput schema / description
      Added value: +"Full metadata for a single dataset."
    • addedOutput schema / properties / dataset
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/DatasetSummary"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / error
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Error"
+}
    • addedOutput schema / properties / extras
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "title": "Extras",
+  "type": "object"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"zurich_get_datasetOutput"New value: +"GetDatasetResult"
  2. First observedv0.3.3

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, indicating safe, non-destructive behavior. The description adds value by specifying the return format (structured JSON plus markdown) and chaining opportunity, but does not disclose any additional behavioral traits like rate limits or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (two sentences plus a returns line), front-loaded with the main purpose, and efficiently conveys key details without extraneous information.

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?

Given the simple single-parameter input, rich annotations, and presence of an output schema, the description sufficiently covers what the tool does, what it returns, and how it connects to other tools, making it complete for its complexity.

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?

The input schema already provides a clear description for the single parameter dataset_id, including examples. The tool description does not add further semantic detail, so it meets the baseline for a well-documented schema parameter.

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 clearly states the tool retrieves complete metadata and resources of a dataset, listing specific fields returned (title, description, author, etc.). It distinguishes from siblings like zurich_datastore_query (query data) and zurich_search_datasets (search), making the purpose specific and unambiguous.

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 implies a usage pattern by mentioning the result can be chained with zurich_datastore_query, providing context for when to use this tool. However, it lacks explicit when-not or alternative recommendations, which is a minor gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/zurich-opendata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server