odpt-mcp

get_station_timetable

Read-onlyIdempotent

Retrieve scheduled Toei rail departures for a station ID, with optional filters for ODPT calendar and rail direction. Use it to build station timetables or check upcoming departures.

Instructions

Get scheduled Toei rail departures by station ID from search_railway.

Filter by full ODPT calendar and rail direction IDs. Departures retain
the provider's service-day order within each timetable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "station_id": "<station_id>"
    },
    "name": "get_station_timetable"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`station_id`	Yes
`calendar_id`	No
`direction_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the lower bar applies. The description adds that results are scheduled departures and preserve the provider's service-day order within each timetable, which is useful operational context; it does not explain pagination behavior.

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 tight sentences, front-loaded with the action and resource, followed by filter and ordering details. No repetition or filler.

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?

The core lookup is clear, annotations cover safety, and an output schema covers return values. However, with five parameters and no schema descriptions, the omission of pagination semantics and limit/offset behavior leaves a clear gap for callers needing controlled result sizes.

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 0%, so the description should carry more parameter meaning. It documents station_id's source and the calendar_id/direction_id filters, but says nothing about limit/offset, leaving two parameters undocumented beyond schema constraints.

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 uses a specific verb and resource ('Get scheduled Toei rail departures') and identifies the station-ID source ('from search_railway'), distinguishing it from search_railway and bus timetable siblings. An agent can tell what it returns 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 Guidelines4/5

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

It tells the caller to obtain the station ID from search_railway and supports filtering by full ODPT calendar and rail direction IDs. It does not explicitly state when to prefer this over search_railway or get_bus_stop_timetable, but the mode-specific context is clear.

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

Deploy Server