Skip to main content
Glama

Hong Kong MTR realtime next-train arrivals at one station

travel_hk_mtr_realtime
Read-only

Hong Kong MTR realtime next-train arrivals at one station on one line, from the Hong Kong government open data feed: direction, destination platform, minutes to next train (ttnt) and scheduled time. Times are the feed's; the feed can be delayed or empty late at night. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "line": "<line>",
      "sta": "<sta>"
    },
    "name": "travel_hk_mtr_realtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
staYesStation code on that line, e.g. TUM, HUH (2 to 4 letters)
lineYesMTR line code, e.g. TML, TCL, ISL, KTL, TKL (2 to 4 letters)

Output Schema

NameRequiredDescriptionDefault
lineNo
countNo
sourceNo
stationNo
arrivalsNo
feedTimeNo
checkedAtNo
isDelayedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the upstream data source, what the payload contains (direction, destination platform, ttnt, scheduled time), a real reliability caveat about delayed or empty feeds at night, and a full billing model ($0.002 per successful call via x402, failed calls not charged). The cost and failure-charging behavior are exactly the kind of operational detail annotations cannot convey.

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?

Purpose is front-loaded in the opening clause, followed by return fields, a reliability caveat, and pricing — each sentence carries distinct information. The payment parenthetical enumerating USDC networks is slightly verbose, but it is relevant to cost-aware invocation rather than filler.

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?

For a two-parameter lookup with an output schema, the definition covers what an agent still needs: data provenance, field meanings, feed reliability limits, and pay-per-call cost. Nothing essential to deciding whether and how to call it is missing.

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%, so both `line` and `sta` are already documented with codes and format examples (2–4 letters). The description only restates the coupling constraint ('one station on one line'), which the schema field description already implies, so it adds little beyond the baseline.

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 verb and resource — 'realtime next-train arrivals at one station on one line' — and names the jurisdiction (Hong Kong MTR) and data source (HK government open data feed). That scope cleanly separates it from sibling rail tools like travel_mbta_realtime, travel_amtrak_train_tracker and travel_septa_train_view without needing to name them.

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 gives clear context for use: one station on exactly one line, realtime arrivals, and a caveat that the feed 'can be delayed or empty late at night', which implicitly tells an agent when results may be unusable. It stops short of stating exclusions or naming an alternative when realtime data is unavailable, so it is not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources