Skip to main content
Glama
Sign In

commutescout

by io.github.nicglazkov
OverviewDiscussionsAdmin

plan_trip

Read-only

Everything about one drive between any two US places, in one call.

Use this for "how's the drive to X", "how long to get to Y at 5",
"anything on the way to Z". It returns:

- the route (miles, main roads, alternatives) from the closure-aware
  planner the CommuteScout map uses: fully closed roads are avoided
  and routes are ranked by what is on them;
- drive time for that departure: with traffic, typical for that
  weekday and hour, and with no traffic (TomTom historical speed
  profiles; live traffic too when leaving within the hour);
- every live event ON the route, ordered by mile: incidents,
  closures, chain controls, message signs, cameras (with image URLs),
  road-weather stations, tolls, speed and red-light cameras, and
  wildfires near it;
- NWS weather alerts along the route and the forecast at the
  destination for the arrival hour;
- a one-paragraph `summary` to lead the answer with, and `notes`
  for anything missing or degraded.

Lead with `summary`, then the items that change the user's plan.
For WHEN to leave, call best_time_to_go instead. If the answer has
needs_clarification, ask the user which option they meant.

Input Schema

NameRequiredDescriptionDefault
originNoAn address, landmark or place anywhere in the US, e.g. '1600 Pennsylvania Ave, Washington DC' or 'Pike Place Market'. Include city and state when you have them. 'home', 'work' or a saved place's name use the user's saved places (see get_my_places). Leave origin out to start from the user's Home.
depart_atNoWhen the user leaves, in the origin's local time: 'now' (default), 'tomorrow 8am', '17:30', 'friday 7:15am' or ISO '2026-11-02T08:00'.
preferenceNoRoute preference.fastest
destinationNoAn address, landmark or place anywhere in the US, e.g. '1600 Pennsylvania Ave, Washington DC' or 'Pike Place Market'. Include city and state when you have them. 'home', 'work' or a saved place's name use the user's saved places (see get_my_places). Leave origin out to start from the user's Home.
origin_coordsNoExact 'lat,lon' instead of a place name, e.g. '47.6097,-122.3421'. Wins over the place name.
destination_coordsNoExact 'lat,lon' instead of a place name, e.g. '47.6097,-122.3421'. Wins over the place name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and open-world; the description adds substantial context beyond them — the closure-aware ranking logic, TomTom historical speed profiles with live traffic only when departing within the hour, inclusion of a `notes` field for missing/degraded data, and a needs_clarification escape hatch. That is exactly the kind of behavioral detail an agent needs before calling a heavy aggregate tool.

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?

Purpose line first, then use cases, then a scannable bulleted return manifest, then output-shaping guidance. Every block is load-bearing; the enumeration of ten event types is on the long side but compensates for the absent output schema.

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?

With no output schema and six optional params, the description carries the return-value burden and does so fully — route, times, on-route events, weather, summary/notes — plus how to order the answer. Nothing material is missing for correct invocation.

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 baseline is 3; the description still adds meaning by tying depart_at to which traffic model is used ('for that departure', live traffic within the hour), which the schema does not say. It does not elaborate on the `preference` enum values, leaving that to 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?

Opens with a specific verb and resource plus scope: 'Everything about one drive between any two US places, in one call.' The enumerated return contents (route, drive time, on-route events, alerts) make it immediately distinguishable from lighter siblings like check_route or rank_routes.

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 concrete user phrasings that select this tool ("how's the drive to X", "anything on the way to Z") and explicitly routes the departure-time decision to best_time_to_go. It also tells the agent how to handle a needs_clarification response. It stops short of excluding the other route-related siblings (check_route, rank_routes), so it isn't fully exhaustive.

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

All commutescout toolsInspect
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