Google Maps MCP Server

roads_nearest

Identify the nearest roads for a set of geographic coordinates, specifying travel mode for accurate road network results.

Instructions

Find nearest roads to given points

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": {
      "points": "<points>"
    },
    "name": "roads_nearest"
  }
}

Input Schema

Name	Required	Description	Default
`points`	Yes	Array of geographic coordinates to find nearest roads for. Each point should be an object like {"lat": 40.7128, "lng": -74.0060}
`travel_mode`	No	Travel mode for road network

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-devJul 6, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It merely restates the name, omitting any details about output format, result count, distance units, or potential limitations like rate limits or data freshness.

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 description is extremely brief (5 words), which is not necessarily concise—it under-specifies. While it avoids fluff, it sacrifices necessary information, making it only marginally acceptable.

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

Completeness1/5

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

For a tool with 2 parameters and no output schema, the description is severely incomplete. It fails to define what 'nearest' means in terms of count or distance, what the output structure looks like, or how travel_mode affects results.

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?

The input schema has 100% coverage, with both parameters (points and travel_mode) already well-described. The description adds no additional semantic meaning beyond the schema, so a baseline score of 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 'Find nearest roads to given points' uses a specific verb ('find') and resource ('nearest roads'), clearly distinguishing this tool from siblings like nearby_find (which finds places) and routes_compute (which computes directions).

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?

The description provides no guidance on when to use this tool versus alternatives such as routes_compute or nearby_find. It does not mention prerequisites or exclusions.

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

Deploy Server