Japan Toilet & Accessibility

get_train_status

Read-onlyIdempotent

Live train service status for Tokyo-area lines — delays, suspensions, resumptions. Ask 'is the Yamanote Line running?' by line or station name, English or Japanese. Status enum: normal / delayed / suspended / resumed. Cause text relayed from ODPT (English summary for known patterns, else original text + null). Data via ODPT (CC BY 4.0).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Line or station name (English or Japanese), e.g. "Yamanote" or "新宿".

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of lines.
`lines`	No	Per-line status: normal / delayed / suspended / resumed, with cause.
`query`	No	Echo of the query.
`stale`	No	True if stale.
`fetched_at`	No	When the snapshot was fetched.
`attribution`	No	Data source(s), license and provenance — an object, or an array of sources.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive. The description adds value by explaining the cause text relay behavior (English summary vs original text) and data attribution to ODPT (CC BY 4.0). No contradictions.

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 concise at four sentences, each providing essential information: purpose, usage example, status enum, and data source. No redundant or missing information.

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?

Given the output schema presence, the description adequately covers the main features (live status, cause text, data source). A small gap: it doesn't mention if multiple results are returned or pagination, but this is minor for a status query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds examples ('Yamanote', '新宿') and clarifies that the query can be in English or Japanese, enhancing the schema description.

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 tool returns live train service status for Tokyo-area lines, including delays, suspensions, and resumptions. It gives specific examples of queries and distinguishes it from sibling tools like get_station_alerts.

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?

The description explains how to use the tool (by line or station name, in English or Japanese) and mentions the status enum and cause text. However, it does not explicitly contrast when to use this tool vs siblings like get_station_alerts or get_active_alerts.

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

All Japan Toilet & Accessibility tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation2/5

Several tools have overlapping purposes: get_active_alerts and get_station_alerts both return JMA flood/landslide alerts, differing only by input type. Similarly, get_municipality_context and get_station_context expose the same underlying data via different resolvers, and get_station_context already includes hazard categories that get_station_hazard duplicates in more detail. These overlaps make it difficult for an agent to know which tool to select for a given query.

Naming Consistency4/5

Most tools follow a clear 'get_' prefix (e.g., get_toilet_by_station, get_train_status), which is consistent. However, 'station_search' and 'ping' break the pattern, and the role-split text references a non-existent 'search_ramen' tool. The dominant convention is clear, but the exceptions introduce minor inconsistency.

Tool Count4/5

With 10 tools, the count is within a reasonable range for the server's broad scope (station info, toilet accessibility, hazards, alerts, train status). However, the redundancy between municipality_context/station_context and actives_alerts/station_alerts means not every tool earns a unique place, making the set slightly over-provisioned. Still, it is not excessively large.

Completeness3/5

The server covers the main info-retrieval needs for toilets, station hazards, alerts, and train status. However, station_search explicitly tells agents to 'search_ramen' for ramen details, yet that tool is not provided, creating a clear dead end. Also, the domain is broader than the server name suggests, and some peripheral data (e.g., detailed ramen profiles) is only partially surfaced.

Resources

Need Help?