Skip to main content
Glama

Neshan travel times to several places

ns_travel_times
Read-onlyIdempotent

Calculates live travel times from one origin to up to 10 destinations by car, motorcycle, bicycle, or walking, ranking them fastest first and separating unroutable points.

Instructions

Get the travel time from one point to several places on Neshan, fastest first.

Ranks ns_search results by real travel time. Each result has to (as given), duration_min (live) and distance_km (car and motorcycle only); unroutable destinations go under failed. Details: ns_route.

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": {
      "origin": "<origin>",
      "destinations": "<destinations>"
    },
    "name": "ns_travel_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTravel mode.car
originYesStart 'lat,lng'.
destinationsYes1-10 end points, each 'lat,lng'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses ordering (fastest first), the meaning of duration_min as live, that distance_km is only returned for car and motorcycle, and that unroutable destinations land under `failed`. This is meaningful behavior for a multi-destination tool; it stops short of stating limits like the 10-destination cap or rate/auth constraints.

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 short sentences, front-loaded with the core action, then ranking semantics, then result fields, then a pointer to the sibling. Nothing is wasted.

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?

With no output schema, the description supplies the result shape (to, duration_min, distance_km, failed) and the ordering guarantee, which is what an agent needs to interpret output. It omits the 1-10 destination cap and mode coverage caveats beyond distance, leaving a small gap.

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; the description earns above that by explaining per-mode output differences and that `to` echoes the destination as given, which the schema does not convey.

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, resource and scope ('travel time from one point to several places', 'fastest first'), and explicitly distinguishes itself from ns_route (details) and ns_search (whose results it ranks). An agent can pick this over ns_route without opening either schema.

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?

Gives clear usage context - ranking ns_search results by real travel time - and routes to ns_route for per-route details. It does not mention ns_transit_route or state when not to use this, so the exclusion set is incomplete.

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