goplaces MCP

Overview Schema Source Related Servers Discussions Admin

Find stops along a route

goplaces_route_search

Read-onlyIdempotent

Find places along a route between two locations, ranked by detour time. Returns detour time plus route distance and duration for stops like coffee or EV charging.

Instructions

Find places along a route between two locations, ranked by how little they detour from it. Returns each result's detour time plus the direct route's distance and duration. Use for requests like 'coffee stops between Seattle and Portland' or 'EV charging on the way to Portland'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Route travel mode.	drive
`limit`	No	Maximum stops to return.
`query`	Yes	Place search text to find along the route, e.g. 'coffee' or 'EV charging'.
`region`	No	Optional CLDR region code, for example 'US' or 'DE'.
`to_text`	Yes	Destination address or place name.
`language`	No	Optional BCP-47 language code, for example 'en' or 'en-US'.
`open_now`	No	When true, only places currently open.
`from_text`	Yes	Origin address or place name.
`include_ev`	No	Include EV charging connectors, charge rates, and availability.
`min_rating`	No	Minimum star rating from 0 to 5.
`detail_level`	No	Field tier to request. Google bills at the most expensive tier in the request, so prefer the cheapest that answers the question: 'ids' returns place IDs only, 'basic' adds name, address, location, type, and a Maps link, and 'full' adds rating, price, hours, phone, and website.	full
`ev_connector_types`	No	Keep only places supporting one of these Google connector types, e.g. ['EV_CONNECTOR_TYPE_CCS_COMBO_2', 'EV_CONNECTOR_TYPE_NACS', 'EV_CONNECTOR_TYPE_J1772', 'EV_CONNECTOR_TYPE_TESLA', 'EV_CONNECTOR_TYPE_CHADEMO', 'EV_CONNECTOR_TYPE_TYPE_2'].
`include_atmosphere`	No	Include the most expensive tier: editorial summary, dine-in/takeout/delivery/reservable, accessibility, and parking options.
`ev_min_charge_rate_kw`	No	Keep only charging stations at or above this rate in kilowatts.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only on failure; the result is also flagged isError.
`route`	No	The direct route the detour times are measured against.
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive. The description adds return-context (detour time, direct route distance and duration) that goes beyond annotations. However, key cost/billing behavior (detail_level tiers, include_atmosphere expense) is only in the schema, not the description.

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?

Three tight sentences: purpose+ranking, returns, and examples. Front-loaded with the core function and no filler.

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?

Given annotations cover safety and the schema fully covers 14 parameters, the description is adequate. It could note the billing-tier tradeoff or the detour-ranking caveat, but for a read-only search with rich schema and output schema, it is nearly complete.

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 coverage is 100%, so every parameter already documents its meaning, including enums, defaults, and billing rationale for detail_level. The description adds no parameter details 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?

States a specific verb (find), resource (places), and scope (along a route between two locations), plus the ranking criterion (least detour). Clearly distinguishable from siblings like goplaces_directions and goplaces_nearby.

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 example queries ('coffee stops between Seattle and Portland', 'EV charging on the way to Portland') that establish when to use it, but doesn't explicitly name alternatives or state when NOT to use it versus goplaces_nearby/search.

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

Deploy Server