Skip to main content
Glama
malkreide

SBB Open Data MCP Server

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SBB Bahnverkehrsstörungen (Live)

sbb_get_rail_disruptions
Read-only

Retrieve current Swiss rail disruptions and alerts with cause, affected lines, and time windows to support real-time monitoring and incident communication.

Instructions

Ruft aktuelle Bahnverkehrsstörungen und -meldungen ab (alle 5 Minuten aktualisiert).

Enthält Titel, Beschreibung, Ursache, Start-/Endzeitpunkt und betroffene Linien. Ideal für Echtzeit-Monitoring und Kommunikation bei Ereignissen.

Args: params (RailDisruptionsInput): Parameter: - limit (int): Max. Meldungen (1–100), Standard 20 - offset (int): Offset für Paginierung - response_format (str): 'markdown' oder 'json'

Returns: str: Liste aktueller Störungsmeldungen mit Zeitfenstern und Beschreibungen. Schema: {title, description, published, start, end, type, author}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesRecords as returned by data.sbb.ch
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "PaginationOutput": {
+      "properties": {
+        "has_more": {
+          "title": "Has More",
+          "type": "boolean"
+        },
+        "next_offset": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Next Offset"
+        },
+        "offset": {
+          "title": "Offset",
+          "type": "integer"
+        },
+        "returned": {
+          "title": "Returned",
+          "type": "integer"
+        },
+        "total_count": {
+          "title": "Total Count",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "total_count",
+        "returned",
+        "offset",
+        "has_more",
+        "next_offset"
+      ],
+      "title": "PaginationOutput",
+      "type": "object"
+    }
+  },
+  "description": "A page of raw data.sbb.ch records plus pagination.",
+  "properties": {
+    "pagination": {
+      "$ref": "#/$defs/PaginationOutput"
+    },
+    "results": {
+      "description": "Records as returned by data.sbb.ch",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Results",
+      "type": "array"
+    }
+  },
+  "required": [
+    "pagination",
+    "results"
+  ],
+  "title": "PagedRecordsOutput",
+  "type": "object"
+}
  2. Changed1 schema field changedv0.3.4
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "sbb_get_rail_disruptionsOutput",
-  "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=true, destructiveHint=false, openWorldHint=true and non-idempotence, so the safety profile is covered. The description adds the 5-minute refresh cadence, which is genuinely useful freshness context, but says nothing about rate limits, auth requirements, or failure behavior for a live open-world source.

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

Conciseness3/5

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

The prose leads with purpose and freshness, which is well front-loaded, but the Returns block restates the output schema that already exists and the Args block duplicates schema descriptions, adding length without new information.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values (its restatement is redundant but harmless). With a single required params object and live data, the definition gives enough for an agent to call it correctly, missing only guidance on alternates and error handling.

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?

Schema description coverage is reported as 0% at the top level, but the Args block mirrors the nested property descriptions (limit 1-100 default 20, offset pagination, response_format markdown/json) without adding new semantics such as pagination interaction or format trade-offs. It compensates for the coverage gap at a minimum-viable level.

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?

States a specific verb and resource ('Ruft aktuelle Bahnverkehrsstörungen und -meldungen ab') with a clear scope qualifier (live, updated every 5 minutes). None of the sibling tools cover rail disruptions, so an agent can distinguish it without opening the schema.

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?

'Ideal für Echtzeit-Monitoring und Kommunikation bei Ereignissen' implies the intended use case, but there is no explicit when-to-use vs when-not guidance and no named alternative among the siblings. Usage is inferred rather than stated.

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