Skip to main content
Glama

routes_compute

Calculate optimal routes between locations using real-time traffic, toll data, and alternative options for driving, walking, cycling, or transit.

Instructions

Calculate optimal routes between locations with real-time traffic data, toll information, and alternative route options. Supports multiple travel modes including driving, walking, cycling, and transit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitsNoUnit system for distances
originYesStarting location for the route. Provide either coordinates like {"lat": 37.7749, "lng": -122.4194} or an address like {"address": "123 Main St, San Francisco, CA"}
regionNoRegion code for biasing results (ISO 3166-1 alpha-2, e.g., "US", "GB", "DE")
languageNoLanguage code for results (ISO 639-1, e.g., "en", "es", "fr")
waypointsNoOptional intermediate stops along the route. Each waypoint should have a "location" (coordinates or address) and optionally "via": true for pass-through points. Example: [{"location": {"lat": 38.0, "lng": -122.0}, "via": false}]
avoid_tollsNoAvoid toll roads
destinationYesEnding location for the route. Provide either coordinates like {"lat": 40.7128, "lng": -74.0060} or an address like {"address": "456 Broadway, New York, NY"}
travel_modeNoTransportation mode for the route
avoid_ferriesNoAvoid ferries
avoid_highwaysNoAvoid highways
routing_preferenceNoRouting algorithm preference
compute_alternative_routesNoWhether to compute alternative routes
Behavior2/5

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

No annotations are provided, so the description carries full weight. It mentions key features but fails to disclose what the output contains (e.g., distances, durations, directions), required permissions, rate limits, or other behavioral traits. The description is insufficient for a complex tool with many parameters.

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?

The description is extremely concise at two sentences, front-loading the core purpose and key differentiators. Every word adds value with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and no output schema, the description lacks crucial details about return values (e.g., route geometry, steps, duration), prerequisites, and common use-cases. It is incomplete for effective agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter already has a description. The tool description adds high-level context (traffic, tolls, modes) but does not enhance understanding of individual parameters beyond what the schema provides. Baseline 3 applies.

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?

The description clearly states the tool's purpose ('Calculate optimal routes between locations') with specific features (real-time traffic, toll information, alternatives) and supported modes (driving, walking, cycling, transit). It distinguishes this from siblings like routes_matrix, which is a different operation.

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?

While the description outlines capabilities, it does not provide explicit guidance on when to use this versus alternatives like routes_matrix or other routing tools. It lacks when-not or exclusion criteria, leaving the agent to infer based on feature listings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/david-pivonka/google-maps-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server