Swisstransport

Search Stations

search_stations

Read-onlyIdempotent

Search for Swiss public transport stations (train, bus, tram) by name query.

Input Schema

Name	Required	Description	Default
`query`	Yes	Station name to search for (e.g., "Zurich HB", "Bern", "Geneva").

Output Schema

Name	Required	Description	Default
`count`	Yes	Number of stations returned
`stations`	Yes	List of matching stations

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Zurich HB"
+  },
+  {
+    "query": "Bern"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stations returned",
+      "type": "number"
+    },
+    "stations": {
+      "description": "List of matching stations",
+      "items": {
+        "properties": {
+          "coordinate": {
+            "description": "Geographic coordinates",
+            "properties": {
+              "x": {
+                "description": "X coordinate (longitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "y": {
+                "description": "Y coordinate (latitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Station identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Station name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stations"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 12, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "query": "Zurich HB"
-  },
-  {
-    "query": "Bern"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Number of stations returned",
-      "type": "number"
-    },
-    "stations": {
-      "description": "List of matching stations",
-      "items": {
-        "properties": {
-          "coordinate": {
-            "description": "Geographic coordinates",
-            "properties": {
-              "x": {
-                "description": "X coordinate (longitude)",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "y": {
-                "description": "Y coordinate (latitude)",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              }
-            },
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Station identifier",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "name": {
-            "description": "Station name",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "stations"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stations returned",
+      "type": "number"
+    },
+    "stations": {
+      "description": "List of matching stations",
+      "items": {
+        "properties": {
+          "coordinate": {
+            "description": "Geographic coordinates",
+            "properties": {
+              "x": {
+                "description": "X coordinate (longitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "y": {
+                "description": "Y coordinate (latitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Station identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Station name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stations"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Zurich HB"
+  },
+  {
+    "query": "Bern"
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare the tool is read-only, idempotent, and non-destructive. The description adds the scope of Swiss public transport and station types, but does not disclose any additional behavioral nuances such as fuzzy matching, pagination, or result ordering. With annotations covering safety, the description provides modest added context.

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 a single, front-loaded sentence with no unnecessary words. It efficiently conveys the action, resource, and scope.

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 tool's simplicity (one parameter, strong annotations, and an output schema), the description is complete. It provides enough information for an agent to invoke the tool correctly without additional explanation.

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 has 100% coverage for the single 'query' parameter, including examples. The description adds no further parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 verb 'Search', the resource 'Swiss public transport stations', and specifies the types (train, bus, tram). This distinguishes it from sibling tools like get_connections and get_stationboard, which operate on station data rather than discover stations by name.

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?

The description implies the tool is for finding stations by name, but it does not explicitly mention when to use it versus alternatives or any exclusions. The sibling tools for connections and stationboards suggest it's a prerequisite, but that connection is not made explicit in the description.

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

All Swisstransport tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Search Stations

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources