Skip to main content
Glama

Route details

route_details
Read-onlyIdempotent

Lists a city's routes with fares, or shows one route: its stops in order in each direction, its fare, the day’s departure times from the first stop and, for routes with live bus positions, where each bus is now. Finds a route by code such as EV5701, by name such as Orange Line, or by service such as Green Electric Bus.

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": {
      "city": "<city>"
    },
    "name": "route_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
routeNoRoute code, name or service. Leave out to list every route in the city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses which fields appear conditionally (live bus positions only for routes equipped with them) and that departure times are the day's from the first stop, not a realtime feed.

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 front-loaded sentences: the return contents come first, the lookup syntax second. The first sentence is long and list-like but every clause names a distinct returned field; the identifier-format sentence is pure added value with no filler.

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?

No output schema exists, so the description must carry return semantics — and it does, naming the specific fields per mode including the conditional live-position case. It does not mention result limits or pagination for the list mode, which is the one remaining gap for a tool that can return every route in a city.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by illustrating the accepted `route` formats — code like EV5701, name like Orange Line, service like Green Electric Bus — which the schema does not enumerate. It also restates the omission-to-list behavior, matching the schema.

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 (lists a city's routes / shows one route) and enumerates exactly what each mode returns: stops in order per direction, fare, day's departures from the first stop, and live bus positions. The dual-mode framing makes it distinguishable from place-level siblings like place_departures and plan_journey.

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 two modes are clearly gated: omit `route` to list every route in the city, supply one to get that route's detail. It gives no guidance on when to prefer plan_journey or place_departures instead, so routing between siblings is left partly to inference.

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.