Skip to main content
Glama

High speed rail fares

thsr_fare
Read-only

Look up Taiwan High Speed Rail single-journey fares between two stations in NT$, including standard, business, and non-reserved cars by passenger type such as adult, child, or senior.

Instructions

THSR single-journey fares between two stations in NT$, per car (standard, business, non-reserved) and passenger type (adult, child, senior, ...). 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_fare"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesArrival THSR station: name (台北, Zuoying, 新竹) or station ID (1000).
fromYesDeparture THSR station: name (台北, Zuoying, 新竹) or station ID (1000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety and data-source openness are covered. The description's added value is the response content dimensions (car class, passenger type, NT$ currency), but it says nothing about live vs. static pricing, caching, or whether both directions return differently-priced results.

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?

One front-loaded sentence carrying purpose, currency, and response dimensions, followed by a short concrete example. No filler, nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must convey the return shape; it names the fare dimensions (standard/business/non-reserved, adult/child/senior) but not the container structure or whether results are a flat list. Adequate to call correctly, but thin for interpreting the response.

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% — both 'from' and 'to' are documented with name-or-ID formats and examples in the schema itself. The description's example ('台北' to '台南') reinforces usage but adds no syntax or constraint information beyond the schema. Baseline 3 applies.

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+resource: single-journey fares between two stations, in NT$, broken out by car class and passenger type. This is clearly a fare-lookup tool, distinguishable in kind from thsr_timetable or thsr_seats, though it never explicitly names those siblings.

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 phrase 'single-journey fares between two stations'. There is no statement of when to pick this over tra_fare or metro_fare, nor any note that it returns fares without schedules or availability. The agent must infer scope from the domain.

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