Skip to main content
Glama
malkreide

SBB Open Data MCP Server

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SBB Open Data Datensätze auflisten

sbb_list_datasets
Read-onlyIdempotent

List all available SBB Open Data datasets to discover new data sources, including dataset IDs, titles, record counts, and update frequencies.

Instructions

Listet alle verfügbaren SBB Open Data Datensätze (data.sbb.ch) auf.

Gibt Dataset-ID, Titel, Anzahl Datensätze und Aktualisierungsfrequenz zurück. Nützlich zur Übersicht und Entdeckung neuer Datensätze.

Returns: str: Vollständige Liste aller SBB Open Data Datensätze. Schema: {dataset_id, title, records_count, update_frequency, themes}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetsYesCatalog entries as returned by data.sbb.ch
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "datasets": {
+      "description": "Catalog entries as returned by data.sbb.ch",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Datasets",
+      "type": "array"
+    },
+    "total_count": {
+      "title": "Total Count",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_count",
+    "datasets"
+  ],
+  "title": "DatasetListOutput",
+  "type": "object"
+}
  2. Changed1 schema field changedv0.3.4
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "sbb_list_datasetsOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the return shape (dataset_id, title, records_count, update_frequency, themes), which is useful context, but says nothing about pagination, result size, or whether the list is unfiltered/complete beyond 'alle'.

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 purpose and use case are front-loaded in two short sentences, which is efficient. The trailing 'Returns:' block is somewhat redundant since an output schema already exists, but it is brief and does not bloat the definition.

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 no-parameter catalog listing tool with annotations covering the safety profile and an output schema covering the return type, the description supplies enough to call it correctly. The only gap is that it restates return fields already documented in the output schema while omitting any note on result volume.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Listet alle verfügbaren SBB Open Data Datensätze ... auf') and names the source domain (data.sbb.ch). It is clearly distinguishable from the sibling getters by resource (a catalog of datasets vs. domain-specific data), though it never explicitly contrasts itself with them.

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?

'Nützlich zur Übersicht und Entdeckung neuer Datensätze' implies a discovery/overview use case, which is reasonable guidance. However, it gives no explicit when-to-use vs. when-not conditions, no mention of how it relates to the sibling retrieval tools, and no prerequisites.

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