Skip to main content
Glama

NS Pros MCP Gateway

google-maps__compute_routes

Computes travel routes between an origin and a destination, optionally through intermediate stops. Returns the distance and duration for each route.

Input Requirements (CRITICAL):

  1. origin and destination (objects - MANDATORY): Each must be provided using exactly one of:

    • address (string, e.g., 'Eiffel Tower, Paris'). Named places, landmarks, and businesses are resolved directly, so do NOT call search_places first just to geocode a waypoint. Include any city, reg

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>",
      "destination": "<destination>"
    },
    "name": "google-maps__compute_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesRequired. Origin waypoint.
travelModeNoOptional. Specifies the mode of transportation.
arrivalTimeNoOptional. Indicates that the route should be computed based on arrival time. Only one of this field or departureTime should be set.
destinationYesRequired. Destination waypoint.
locationBiasNoOptional. A location to bias the search results toward, for example to disambiguate waypoint text queries.
departureTimeNoOptional. Indicates that the route should be computed based on departure time. Only one of this field or arrivalTime should be set.
includePolylineNoOptional. Whether to include the encoded polyline in the response routes. Defaults to `false`. When set to `true`, `Route.encoded_polyline` is returned.
routingPreferenceNoOptional. Determines how traffic data is used to compute the route. `ROUTING_PREFERENCE_TRAFFIC_AWARE_OPTIMAL` is not supported when `travel_mode` is `WALK` or `BICYCLE`. For `TRANSIT`, it enables realtime transit data, such as delays and cancellations.
intermediateWaypointsNoOptional. Intermediate stops between the origin and destination to pass through in order. Up to 25 intermediate waypoints are supported. Specifying more than 10 intermediate waypoints will incur higher cost and higher latency. Intermediate waypoints are not supported when `travel_mode` is `TRANSIT`.
computeAlternativeRoutesNoOptional. Whether to compute alternative routes in addition to the recommended route. Defaults to false, in which case only the recommended route is returned. When set to true, up to all available routes are returned, though alternatives may not be available for every request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the essential return shape (distance and duration per route) and that multiple routes may come back, but says nothing about cost/billing tiers, latency, or failure modes when a waypoint cannot be resolved — cost signals only appear buried in the schema's enum text.

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?

The summary is front-loaded in two tight sentences and the input requirements are organized with bold headers and numbering. However, the text is truncated mid-sentence ('Include any city, reg'), leaving a visibly incomplete fragment and a top-heavy CRITICAL banner that promises more than is delivered.

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

Completeness3/5

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

This is a 10-parameter routing tool with no output schema and no annotations, so the description should be the main behavioral reference. It covers only the first input requirement before being cut off, leaving travel mode selection, departure/arrival time, waypoint limits, and alternative-route behavior undocumented outside the schema.

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 the schema already documents all ten parameters including enum semantics. The description reinforces the origin/destination 'exactly one of address/latLng/placeId' rule and clarifies that addresses resolve named places, but this largely repeats what the Waypoint schema states.

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 opening sentence states a specific verb and resource ('Computes travel routes') plus scope ('between an origin and a destination, optionally through intermediate stops') and declares the return payload ('distance and duration for each route'). That is enough to distinguish it from siblings like search_along_route or resolve_names without opening the 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?

It gives an explicit negative routing rule: named places are resolved directly, so the agent should NOT call search_places first just to geocode a waypoint. That is real when-not guidance against a named sibling. It stops short of saying when to prefer search_along_route or how to choose between travel modes, and the guidance list cuts off mid-item.

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.