odpt-mcp

get_train_status

Read-onlyIdempotent

Retrieve Toei rail service notices with provider timestamps and expiry dates; optionally filter by a line ID to check current disruptions and verify valid_until before use.

Instructions

Get Toei rail service notices with provider timestamps and expiry.

Supply a line ID from search_railway to restrict the notices. An empty
result means the API returned no matching notices. Check valid_until
before using a notice as current information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_train_status"
  }
}

Input Schema

Name	Required	Description	Default
`line_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 readOnly, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description still adds real context beyond them: that an empty result means no matches rather than an error, and that notices carry provider timestamps and an expiry field that must be checked before use.

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?

Four short sentences, front-loaded with the resource, then filtering, then result interpretation, then caveat. The empty-result sentence is slightly defensive but earns its place by preventing misinterpretation of a null response.

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?

An output schema exists, so return values need not be described, and the description still flags the key output field (valid_until). For a single optional-parameter read tool, nothing required to call it correctly is missing.

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 0%, so the description must compensate, and it does: it identifies the line_id parameter's semantics (restricts the notice set), its provenance (from search_railway), and implicitly its optionality by describing the unfiltered case. It does not explain the expected ID format or pattern, leaving the schema regex to carry that alone.

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?

States a specific verb and resource: "Get Toei rail service notices with provider timestamps and expiry." The subject matter (service notices) is distinct from the sibling fare, timetable, and search tools, though the description never explicitly contrasts itself with the closest-sounding sibling like get_station_timetable.

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?

Gives a clear usage path: pass a line ID from search_railway to narrow results, and check valid_until before treating a notice as current. It does not state when to avoid this tool or name a direct alternative, so it falls short of explicit when/when-not guidance.

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

Deploy Server