Skip to main content
Glama
ymyzk

Nagoya Bus MCP

by ymyzk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_timetable

Retrieve formatted bus timetable for a station, including routes, directions, boarding locations, and departure times organized by day of week.

Instructions

Get formatted timetable information for all routes at a station.

Retrieves and formats timetable data including routes, directions, boarding locations, and departure times organized by day of week.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
station_numberYesThe station number to query (e.g., 22460).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes系統別の時刻表一覧のURL
timetablesYes
station_numberYesバス停番号

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / station_number / description
      Added value: +"The station number to query (e.g., 22460)."
    • removedInput schema / properties / station_number / title
      Removed value: -"Station Number"
    • removedOutput schema / $defs
      Removed value: -{
-  "TimeTable": {
-    "properties": {
-      "direction": {
-        "description": "方面",
-        "title": "Direction",
-        "type": "string"
-      },
-      "pole": {
-        "description": "乗り場",
-        "title": "Pole",
-        "type": "string"
-      },
-      "route": {
-        "description": "路線",
-        "title": "Route",
-        "type": "string"
-      },
-      "stop_stations": {
-        "description": "停車バス停のリスト",
-        "items": {
-          "type": "string"
-        },
-        "title": "Stop Stations",
-        "type": "array"
-      },
-      "timetable": {
-        "additionalProperties": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "description": "曜日別の時刻表",
-        "title": "Timetable",
-        "type": "object"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "route",
-      "direction",
-      "pole",
-      "stop_stations",
-      "timetable",
-      "url"
-    ],
-    "title": "TimeTable",
-    "type": "object"
-  },
-  "TimeTableResponse": {
-    "properties": {
-      "station_number": {
-        "title": "Station Number",
-        "type": "integer"
-      },
-      "timetables": {
-        "items": {
-          "$ref": "#/$defs/TimeTable"
-        },
-        "title": "Timetables",
-        "type": "array"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "station_number",
-      "timetables",
-      "url"
-    ],
-    "title": "TimeTableResponse",
-    "type": "object"
-  }
-}
    • addedOutput schema / description
      Added value: +"Response model for station timetable queries.\n\nContains all timetables for different routes operating at a given station,\nalong with the station identifier and reference URL."
    • removedOutput schema / properties / result
      Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/TimeTableResponse"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • addedOutput schema / properties / station_number
      Added value: +{
+  "description": "バス停番号",
+  "type": "integer"
+}
    • addedOutput schema / properties / timetables
      Added value: +{
+  "items": {
+    "description": "Timetable information for a single route at a station.\n\nContains route details, direction, boarding location, and departure times\norganized by day of week.",
+    "properties": {
+      "direction": {
+        "description": "行き先",
+        "type": "string"
+      },
+      "pole": {
+        "description": "のりば",
+        "type": "string"
+      },
+      "route": {
+        "description": "系統",
+        "type": "string"
+      },
+      "route_codes": {
+        "description": "系統コードのリスト",
+        "items": {
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "stop_station_names": {
+        "description": "停車バス停名のリスト",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "timetable": {
+        "additionalProperties": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "description": "曜日別の時刻表",
+        "type": "object"
+      },
+      "url": {
+        "description": "系統の時刻表のURL",
+        "type": "string"
+      }
+    },
+    "required": [
+      "route",
+      "route_codes",
+      "direction",
+      "pole",
+      "stop_station_names",
+      "timetable",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / url
      Added value: +{
+  "description": "系統別の時刻表一覧のURL",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "station_number",
+  "timetables",
+  "url"
+]
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions retrieval and formatting but does not clarify if it is read-only, what happens if the station does not exist, or any other important side effects or constraints.

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?

Two concise sentences: the first states the primary action, the second elaborates on the content. No redundant or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description sufficiently covers the tool's functionality. However, it lacks usage guidance and differentiation from sibling tools, which would improve completeness.

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 schema covers the only parameter (station_number) with a description including an example. The tool description does not add extra meaning beyond what the schema already provides, so it meets the baseline for high coverage.

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 clearly states it retrieves formatted timetable information for all routes at a station, using a specific verb and resource. However, it does not explicitly distinguish itself from sibling tools like get_approach_for_route, which fetch more specific data.

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 provides no guidance on when to use this tool versus alternatives (e.g., getting approach info for a specific route). It only describes what it does, leaving the agent to infer usage 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