Skip to main content
Glama

commute_time

Read-onlyIdempotent

Minutes from home (from) to work (to), same model as the Dojazdomat map (czas dojazdu z domu do pracy). transit: door to door by public transport plus walking, weekday 7-9 average, with the nearest stops at both ends; bike, walk: OpenStreetMap paths (bike +2 min); car: rush-hour driving. minutes is null when unreachable (over 90 min).

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_lat": "<from_lat>",
      "from_lon": "<from_lon>",
      "to_lat": "<to_lat>",
      "to_lon": "<to_lon>"
    },
    "name": "commute_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNotransit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, autotransit
to_latYesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
to_lonYesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
from_latYesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
from_lonYesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "default": "transit",
      +  "description": "transit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, auto",
      +  "enum": [
      +    "transit",
      +    "bike",
      +    "walk",
      +    "car"
      +  ],
      +  "title": "Mode",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the underlying model (Dojazdomat), the weekday 7-9 transit averaging window, a bike +2 min adjustment, and the rule that minutes is null beyond 90 minutes. It doesn't state whether results are cached or how precision degrades outside the modeled window, keeping it below a 5.

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?

Front-loaded with the core definition, then per-mode detail and the null rule — every clause carries information. Slightly dense with repeated Polish aliases (Dojazdomat / czas dojazdu z domu do pracy) and mode wording that partially duplicates the schema's mode description.

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?

For a 5-parameter geospatial tool with an output schema, the description covers the modeling assumptions, the geographic restriction (via schema), and the unreachable case. An agent can call it correctly; only edge behavior such as rounding or result granularity is unspecified, and the output schema likely covers the return shape.

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 adds real meaning: 'from' is home and 'to' is work, and the mode enum values are tied to concrete modeling assumptions (transit = weekday morning average with nearest stops at both ends, car = rush hour, bike/walk = OSM paths). This meaningfully supplements the enum's own one-line description.

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 concrete computation (minutes from a 'from' point to a 'to' point) with per-mode semantics, so an agent knows exactly what is returned. It does not name or contrast itself with any sibling such as reachable_neighborhoods or rank_neighborhoods, leaving the routing to the caller.

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?

The description explains what each mode means (transit = weekday 7-9 door-to-door plus walking, car = rush hour), which implicitly tells the agent when a given mode is appropriate. It gives no explicit when-to-use vs. when-not-to-use guidance or named alternatives, so the choice against sibling tools is left 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.

Resources