Skip to main content
Glama
malkreide

SBB Open Data MCP Server

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SBB Immobilien-Bauprojekte

sbb_get_real_estate_projects
Read-onlyIdempotent

Fetch ongoing SBB real estate projects with filters for city and phase; get project names, construction stages, move-in dates, and usable area.

Instructions

Ruft laufende SBB-Immobilien-Bauprojekte (Wohn- und Geschäftsbauten) ab.

Täglich aktualisiert. Enthält Projektname, Stadt, Bauphase, Nutzfläche, Baudaten und Beschreibungen (DE/FR/IT/EN).

Args: params (RealEstateProjectsInput): Parameter: - city (Optional[str]): Stadt, z.B. 'Zürich', 'Bern', 'Luzern' - phase (Optional[str]): Projektphase, z.B. 'CONSTRUCTION', 'PLANNING' - limit (int): Max. Resultate - offset (int): Paginierung - response_format (str): 'markdown' oder 'json'

Returns: str: Immobilien-Bauprojekte mit Baustart, Einzug und Nutzfläche. Schema: {title, city, phase, start_of_construction, move_in, area_m2, description}

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_real_estate_projectsOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.8/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 by structured data. The description adds genuinely useful non-redundant context — daily refresh cadence and multilingual descriptions (DE/FR/IT/EN) — but omits auth requirements, rate limits, and pagination behavior, and partly restates the output fields.

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?

Purpose is front-loaded well, but the boilerplate Args and Returns blocks largely duplicate what the input and output schemas already define, adding length without new meaning. The Returns section in particular restates fields the output schema already carries.

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 read-only, annotated, output-schema-backed data tool, the definition covers purpose, cadence, language coverage, filter dimensions, and pagination. Complete enough to invoke correctly, with only the phase-enum mismatch and absent auth/limit details as nits.

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?

Schema description coverage is reported at 0%, so the description must carry the parameter burden, and it mostly does: city with concrete examples, phase with example values, limit/offset semantics, and the two response_format options. Minor gap: the phase examples ('CONSTRUCTION', 'PLANNING') omit 'COMPLETED' which the nested schema lists, a small inconsistency an agent could trip over.

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 (abrufen/retrieve), a precise resource (laufende SBB-Immobilien-Bauprojekte), and scopes it to Wohn- und Geschäftsbauten. Nothing in the sibling list overlaps with real estate projects, so an agent can immediately tell this apart from the station, rolling-stock, or disruption tools.

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?

Usage is implied by the resource itself, and the daily-update note hints at freshness expectations. However, there is no explicit when-to-use guidance, no statement of prerequisites, and no exclusions or alternatives named. For a standalone tool with no close sibling this is acceptable but thin.

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