Skip to main content
Glama

High speed rail seat availability

thsr_seats
Read-only

Check THSR reserved-seat availability by station pair and date, showing standard and business class status and departure times, with data updated about every 10 minutes.

Instructions

Reserved-seat availability (available, limited, sold out) in standard and business class for THSR trains between two stations, with their times. Updated about every 10 minutes. Example: from "台北", to "台中".

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "thsr_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesArrival THSR station: name (台北, Zuoying, 新竹) or station ID (1000).
dateNoTravel date in Taiwan, YYYY-MM-DD (default: today).
fromYesDeparture THSR station: name (台北, Zuoying, 新竹) or station ID (1000).
afterNoOnly departures at or after this time, HH:mm (default: now for today, else 00:00).
limitNoMaximum number of trains to return (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / after / description
      Previous value: -"Only trains departing at or after this time, HH:mm (default: now for today, else 00:00)."New value: +"Only departures at or after this time, HH:mm (default: now for today, else 00:00)."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond annotations: data freshness ('updated about every 10 minutes') and the closed vocabulary of availability values. It does not clarify scope limits (e.g., whether non-reserved/free seats are excluded) or behavior for past dates, but readOnlyHint already covers the safety profile.

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?

Two sentences, front-loaded with the returned resource before the freshness note and example. The trailing example slightly duplicates the schema's own station examples but costs little.

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?

For a read-only, no-output-schema query, the description says what comes back (availability state per class with times), which is the key missing piece. Minor gaps remain around coverage of seat types and empty-result behavior.

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 coverage is 100% and every parameter is documented there, including station name/ID forms and defaults. The description's example merely restates accepted input syntax already given by the schema, so it adds no new semantics.

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 resource (reserved-seat availability) with the exact return values (available, limited, sold out), both classes, and station pair plus times. An agent can distinguish it from timetable/fare tools, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the example ('from 台北, to 台中'); there is no statement of when to prefer this over thsr_timetable or thsr_train, nor any precondition such as requiring a travel date.

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