Skip to main content
Glama

Find rail stations

rail_station_search
Read-only

Search rail stations by Chinese or English name or nearest coordinate to retrieve station IDs, explore a rail system, find the closest station, or resolve ambiguous names.

Instructions

Stations of a rail system by name (Chinese or English) or nearest to a coordinate, with their IDs. The other rail tools accept names directly, so use this to explore, to find the nearest station, or when a name is ambiguous. Example: system "TRTC", lat 25.0478, lon 121.517; or system "TRA", keyword "新竹".

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": {
      "system": "<system>"
    },
    "name": "rail_station_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, to sort by distance.
lonNoLongitude, to sort by distance.
limitNoMaximum number of stations to return (default 10).
systemYesRail system: THSR (高鐵 high speed rail), TRA (臺鐵 Taiwan Railway), AFR (阿里山林業鐵路), or a metro: TRTC 臺北捷運 Taipei Metro, NTMC 新北捷運 (環狀線) New Taipei Metro, TYMC 桃園機場捷運 Taoyuan Airport MRT, TMRT 臺中捷運 Taichung MRT, KRTC 高雄捷運 Kaohsiung MRT, KLRT 高雄輕軌 Kaohsiung LRT, NTDLRT 淡海輕軌 Danhai LRT, NTALRT 安坑輕軌 Ankeng LRT, TRTCMG 貓空纜車 Maokong Gondola.
keywordNoPart of the station name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results carry IDs and that names may be ambiguous, but says nothing about what happens when keyword and coordinates are supplied together, how limit interacts with distance sorting, or whether a bad system code errors out. With annotations doing the heavy lifting, this is adequate but not rich.

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 sentences plus a dual example, front-loaded with the capability, then the routing rule, then concrete invocations. Every clause carries information; nothing is repeated from the title or schema.

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?

With no output schema, the description usefully notes that station IDs are returned, and the schema documents all five parameters including defaults and limits. The only real gap is precedence/combination behavior between keyword and coordinate inputs, which an agent must guess.

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 100%, including a fully enumerated system field with bilingual expansion, so the schema carries parameter meaning on its own. The examples do show how system combines with lat/lon versus keyword, which adds a little value beyond per-parameter docs, but not enough to exceed the baseline by much.

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?

States a specific resource (rail stations), two lookup modes (by name in Chinese/English, or nearest to a coordinate) and a key output detail (station IDs). It also distinguishes itself from the surrounding rail tools by noting those accept names directly, so an agent can tell this is the lookup/exploration primitive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly gives the when-to-use conditions: explore, find the nearest station, or resolve an ambiguous name — and implicitly gives when-not-to-use by saying other rail tools take names directly. The two worked examples (TRTC with lat/lon, TRA with a Chinese keyword) anchor each mode concretely.

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