google-maps-mcp

Maps Plan Route

maps_plan_route

Read-onlyIdempotent

Plan multi-stop routes, optimize stop order, and estimate distance, duration, and arrival times for driving, walking, or cycling.

Instructions

Plan a multi-stop route: {travelMode, optimized, order (indices of stops in the chosen order), ordersCompared, savedVsGivenOrder, description, distanceMeters, duration, durationWithDwell, departureTime, arrivalTime, timeZone, stops [{label, role, inputIndex, query, displayName, formattedAddress, placeId, location, arrivalOffset, arrivalTime, dwellMinutes, departureTime, openingStatus {state, text, hours}, rating, category}], legs [{from, to, distanceMeters, duration, staticDuration}], warnings, googleMapsUri}. Without departureTime the plan starts now.

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>",
      "stops": "<stops>"
    },
    "name": "maps_plan_route"
  }
}

Input Schema

Name	Required	Description	Default
`stops`	Yes	Places to visit (up to 8)
`origin`	Yes	A place name or address ('Albertina, Vienna'), a place id (ChIJ…) or 'lat,lng'
`roundTrip`	No	Come back to the origin
`travelMode`	No	DRIVE (default), WALK or BICYCLE	DRIVE
`destination`	No	Fixed end; omit to end at the last stop
`dwellMinutes`	No	Minutes at each stop, in the order given
`departureTime`	No	Local wall-clock time at the stop, e.g. 2026-10-22T08:30 (no offset)
`optimizeOrder`	No	Find the fastest order of the stops

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Oct 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so nothing contradicts them. The single genuinely useful disclosure is "Without departureTime the plan starts now"; beyond that, the text enumerates return fields instead of explaining behavior such as whether optimizeOrder can reorder the input stops or how dwell time affects arrival calculations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bulk of the text is a 20+ field enumeration of the response (stops[{...}], legs[{...}], warnings, googleMapsUri), which duplicates an existing output schema. It is structurally front-loaded but bloated with material that does not earn its place.

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?

An output schema already exists, so restating every return field adds nothing. Meanwhile the description omits details an agent actually needs, such as how order relates to optimizeOrder=false, or what warnings mean. It is verbose in the wrong place and thin where it matters.

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 every parameter including stops, origin, optimizeOrder, and dwellMinutes is already documented in the schema. The description contributes only the departureTime default note, which is worth little against the schema's own detail. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Plan a multi-stop route" gives a concrete verb+resource, but the rest of the description is a field dump rather than further explanation. It never distinguishes this from sibling tools like maps_compute_route or maps_show_route, which an agent could easily confuse with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus maps_compute_route (single-leg routing) or maps_show_route (render an itinerary). The only usage hint is a trailing note about departureTime defaulting to now, which is behavioral rather than selection guidance.

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

Deploy Server