Skip to main content
Glama

NS Pros MCP Gateway

google-maps__search_along_route

Call this tool when the user wants to find places, businesses, or points of interest along a travel route (e.g., "gas stations on my way to Tahoe", "coffee shops between SF and San Jose"). Calling this tool incurs higher cost than search_places, so use search_places instead when searching near a single location rather than along a route.

Input Requirements (CRITICAL):

  1. text_query (string - MANDATORY): A natural language description of what to search for along the route. *

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": {
      "textQuery": "<textQuery>"
    },
    "name": "google-maps__search_along_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
textQueryYesRequired. Natural language search query (e.g., "ev chargers", "coffee").
regionCodeNoOptional. Country/region code (CLDR) of location (e.g., "US").
travelModeNoOptional. Specifies the travel mode used to compute the route and the detours. Defaults to `DRIVE`. `WALK` and `BICYCLE` are only supported with `route_endpoints`. `TRANSIT` is not supported.
languageCodeNoOptional. The language for summary and place details. Defaults to "en-US".
retrievalTokenNoA retrieval token returned from a prior ComputeRoutes call representing the route. Only one of the following fields should be set: this field, encodedPolyline, routeEndpoints.
routeEndpointsNoExplicit route endpoints (origin and destination). Only one of the following fields should be set: this field, encodedPolyline, retrievalToken.
encodedPolylineNoAn encoded polyline string representing the route. See https://developers.google.com/maps/documentation/utilities/polylinealgorithm. Only one of the following fields should be set: this field, retrievalToken, routeEndpoints.
routingPreferenceNoOptional. Optional routing preference specifying how traffic data is used. Defaults to TRAFFIC_UNAWARE.
includeExtendedDetailsNoOptional. Includes extended place details in the response. Set this field to `true` when the user request requires rich qualitative insights, real-time dynamics, or specialized entity attributes: - Qualitative reviews, customer sentiment, and feedback. - Specific offerings like menu items, dishes, food specialties, beverages, or business highlights. - Qualitative atmosphere, interior decor, aesthetic, ambience, or mood. - Real-time data and specialized facility specs, visitor policies/tips, wait times. Leave `false` (default) for standard discovery searches (e.g., cuisines, store types), location/address lookups, contact info, operating hours, and standard metadata/amenities. Enabling this field may incur higher latency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the notable behavioral trait that this call 'incurs higher cost than `search_places`'. However, the 'Input Requirements (CRITICAL)' section that follows is truncated and largely restates schema field descriptions rather than adding behavioral detail about results, latency, or failure modes.

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

Conciseness3/5

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

The opening is well front-loaded, leading with the trigger condition and the cost/alternative guidance. But the definition then begins a structured restatement of each parameter already fully documented in the schema, and the trailing truncation suggests padding rather than earned content.

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?

For a 9-parameter, no-annotation, no-output-schema tool, the description covers selection and cost well but says nothing about the shape of results, how many places are returned, or how route specification variants behave in practice. It is adequate to invoke the tool but not 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 description coverage is 100%, so the schema already documents all 9 parameters, including the mutually exclusive route-specification fields and enum behavior. The description's 'Input Requirements' section adds emphasis ('MANDATORY') but no syntax or format information beyond what the schema already provides; baseline 3 is appropriate.

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 uses an explicit trigger phrase naming the verb and resource ('find places, businesses, or points of interest along a travel route') and immediately grounds it with concrete examples ('gas stations on my way to Tahoe'). It also names the sibling it is not (`search_places`), so an agent can discriminate the two without opening schemas.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition (searching along a route) and an explicit when-not-to/alternative (use `search_places` for a single location), justified by a concrete cost difference. This is exactly the routing guidance an agent needs.

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.