Skip to main content
Glama

Travel times between places

travel_times
Read-onlyIdempotent

Compute road distance and travel time matrices between Indian places by car or on foot using coordinates, railway stations, airports, or place names. Returns road km and traffic-aware minutes.

Instructions

Computes road distance and travel time from each origin to each destination in India (a matrix), by car or on foot. Each place is lat+lng, a railway station code, an airport IATA code or a place name. Returns straight-line km, road km, free-flow minutes and traffic-adjusted minutes per pair, with a warning when a point is far from any road. Does not cover public transport or flights.

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": {
      "origins": "<origins>",
      "destinations": "<destinations>"
    },
    "name": "travel_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodrive (car/taxi, with traffic allowance) or walk.drive
originsYesStarting places.
destinationsYesDestination places.

Output Schema

NameRequiredDescriptionDefault
legsYesOne leg per origin–destination pair, origin by origin.
notesYesHow times are computed, and attribution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.0
    • addedOutput schema / properties / legs / description
      Added value: +"One leg per origin–destination pair, origin by origin."
    • addedOutput schema / properties / legs / items / properties / from / description
      Added value: +"Label of the origin."
    • addedOutput schema / properties / legs / items / properties / minutes / description
      Added value: +"Travel time after the traffic multiplier, minutes; equals minutes_raw for walking (null when no route)."
    • addedOutput schema / properties / legs / items / properties / minutes_raw / description
      Added value: +"Free-flow travel time from the router, minutes (null when no route)."
    • addedOutput schema / properties / legs / items / properties / road_km / description
      Added value: +"Road distance along the route, km (null when no route was found)."
    • addedOutput schema / properties / legs / items / properties / straight_km / description
      Added value: +"Straight-line distance, km."
    • addedOutput schema / properties / legs / items / properties / to / description
      Added value: +"Label of the destination."
    • addedOutput schema / properties / legs / items / properties / traffic_multiplier / description
      Added value: +"Factor applied to free-flow drive time for traffic, higher in metro areas; 1 for walking."
    • addedOutput schema / properties / legs / items / properties / warning / description
      Added value: +"Set when no route was found or a point is over 500 m from the nearest road."
    • addedOutput schema / properties / notes / description
      Added value: +"How times are computed, and attribution."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact per-pair outputs (straight-line km, road km, free-flow and traffic-adjusted minutes) and the warning emitted when a point is far from any road, plus the fact that place names are resolved to a 'best match'.

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?

Three tight sentences: purpose and scope first, accepted input identifiers second, returned values plus failure warning third. No filler, no repetition of the title, and the most decision-relevant constraint (India, road/walk only) is front-loaded.

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?

An output schema exists, so return values did not need to be spelled out, yet the description helpfully names the key per-pair metrics and the far-from-road warning. Combined with the schema's bounds (max 10 origins, 25 destinations, India lat/lng limits) and the annotations' read-only profile, an agent has everything needed to call this correctly.

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 and the schema already documents every parameter including the four point identifier kinds and the drive/walk enum. The description adds meaning on top by summarizing that each place may be lat+lng, a station code, an IATA code or a place name, and by noting that names are resolved to their best match rather than exact-matched.

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 ('Computes road distance and travel time from each origin to each destination in India (a matrix)') plus the supported modes, so the agent knows exactly what operation this is. It also delineates scope by naming what it does not cover (public transport, flights), which no sibling does, cleanly separating it from the hotel/place siblings.

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 establishes clear context for use: India-only, drive-vs-walk mode, and the matrix (each-to-each) semantics, plus an explicit exclusion of public transport and flights. It stops short of naming an alternative tool (e.g. resolve_place for ambiguous place resolution), so it is strong but not fully routing-oriented.

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