Get Around Hong Kong

Look up a Hong Kong bus route or MTR line

search_routes

Read-only

Hong Kong bus and green minibus routes by number, and MTR lines by name or code, the same as typing one in the site's Nearby box: where each runs between, its operator, its first and last departures by day, and this site's page for it (every stop, fares, live arrivals). A number can be several routes (route 40 is Citybus, KMB and three minibus routes in different districts): all are returned, each with its ends. Special services (a supplementary or short-working run) are left out once they have no departure left today. For travelling somewhere, use plan_trip.

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": {
      "query": "<query>"
    },
    "name": "search_routes"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Only buses, green minibuses or MTR lines
`query`	Yes	A route number or line: "40", "N21", "A21", "28M", "Island Line", "港島綫", "TWL"
`language`	No	Language for place and line names: en, zh-HK (Traditional Chinese), zh-CN (Simplified), ja, ko	en

Output Schema

Name	Required	Description	Default
`query`	Yes
`routes`	Yes	Every route matching: a number names all operators' and districts' routes with it. Empty when none does

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it explains that ambiguous route numbers return all matching routes, lists what each result contains, and notes that special services are omitted once they have no departure left today. These details are important for interpreting results and are not merely restatements of readOnlyHint or openWorldHint.

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?

The description is front-loaded with the core lookup behavior and every sentence contributes useful context. The first sentence is dense and slightly run-on, but the overall structure remains efficient.

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 read-only search tool with a full output schema and annotations, the description covers the essential semantics: input interpretation, ambiguous-match behavior, filtering of special services, and the main alternative tool. Nothing critical is missing.

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

Parameters4/5

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

With 100% schema description coverage, the schema already documents all three parameters. The description still adds useful query semantics by clarifying that a number can match multiple routes and that MTR lines may be searched by name or code, though it does not discuss the language parameter specifically.

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 states a specific lookup operation for Hong Kong bus/minibus routes by number and MTR lines by name or code, including the exact output categories such as endpoints, operator, first/last departures, and the site page. It clearly distinguishes route lookup from travel planning by naming plan_trip as the alternative.

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?

It explains the lookup use case directly and gives an explicit exclusion: 'For travelling somewhere, use plan_trip.' The comparison to typing a route into the site's Nearby box further anchors when this tool is appropriate.

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

All Get Around Hong Kong tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?