Skip to main content
Glama
malkreide

SBB Open Data MCP Server

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SBB Züge pro Streckenabschnitt

sbb_get_trains_per_segment
Read-onlyIdempotent

Retrieve train counts per route segment and traffic type for Swiss rail operators, including passenger and freight traffic, track kilometers, and electricity use.

Instructions

Ruft Anzahl Züge pro Streckenabschnitt und Verkehrstyp ab.

Deckt SBB, BLS, SOB, DB und weitere Infrastrukturbetreiberinnen ab. Enthält Personenverkehr und Güterverkehr, Trassenkilometer und Stromverbrauch.

Args: params (TrainsPerSegmentInput): Parameter: - line_name (Optional[str]): Streckenbezeichnung (Teilsuche) - operator (Optional[str]): Infrastrukturbetreiberin, z.B. 'SBB', 'BLS' - year (Optional[str]): Jahr, z.B. '2025' - traffic_type (Optional[str]): 'Personenverkehr' oder 'Gueterverkehr' - limit (int): Max. Resultate - offset (int): Paginierung - response_format (str): 'markdown' oder 'json'

Returns: str: Zugzahlen pro Streckenabschnitt mit Operator und Traffiktyp. Schema: {segment, line, operator, year, train_count, traffic_type, track_km}

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. Changed2 schema fields changedv0.3.4
    • changedInput schema / $defs / TrainsPerSegmentInput / properties / year / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\d{4}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "sbb_get_trains_per_segmentOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

B3.2/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 structurally. The description adds useful content-scope context (multiple operators, passenger + freight, track km, electricity consumption) but nothing about rate limits, auth, or pagination behaviour beyond restating offset/limit.

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?

Front-loaded summary followed by a compact scope paragraph and structured Args/Returns blocks. It is somewhat repetitive relative to the schema, but every part is legible and there is no padding.

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?

With an output schema present, the description need not explain return values, but it still names the returned fields, and it covers the query dimensions an agent needs to know. It is complete enough to call correctly; only the missing sibling routing keeps it from being fully self-sufficient.

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 Args block essentially restates the schema, which already carries descriptions for year, operator, line_name and traffic_type. It adds no format hints, matching semantics, or enum details beyond what the schema provides, so it sits at the baseline for schema-documented parameters.

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?

The description gives a specific verb and resource ('Ruft Anzahl Züge pro Streckenabschnitt und Verkehrstyp ab') and clarifies scope by naming the covered operators (SBB, BLS, SOB, DB) and the fact that both passenger and freight traffic are included. It does not, however, differentiate itself from the closest sibling sbb_get_passenger_frequency, which likely overlaps in subject matter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what data the tool returns but offers no guidance on when to choose it over siblings such as sbb_get_passenger_frequency or sbb_get_platform_data. There are no stated preconditions, exclusions, or alternative-routing cues beyond an implied context.

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