google-maps-mcp-server

get_directions

Get route directions between any two locations with real-time traffic data, distance, and duration. Supports driving, walking, bicycling, and transit modes.

Instructions

Get route directions between origin and destination with real-time traffic data. Returns routes with distance, duration, steps, and traffic information.

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": "get_directions"
  }
}

Input Schema

Name	Required	Description	Default
`origin`	Yes	Starting location (address or 'lat,lng')
`destination`	Yes	Ending location (address or 'lat,lng')
`mode`	No	Travel mode	driving
`departure_time`	No	ISO 8601 timestamp for departure (for traffic estimation)
`alternatives`	No	Return alternative routes
`avoid`	No	Features to avoid
`traffic_model`	No	Traffic prediction model	best_guess

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Mentions real-time traffic and returned fields (distance, duration, steps, traffic info). Lacks details on potential errors, max routes, or authorization needs.

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?

Single sentence, no wasted words. Efficiently conveys purpose and output.

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?

Adequate for a 7-param tool with no output schema or annotations. Covers basic purpose and output, but omits behavior details like default mode, how alternatives work, and error handling.

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 baseline is 3. Description adds that real-time traffic is supported, which relates to departure_time and traffic_model, but doesn't add meaning beyond schema descriptions.

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?

Clearly states 'Get route directions between origin and destination with real-time traffic data.' Verb is specific, resource is route directions. Distinguishes from siblings like calculate_distance_matrix and get_traffic_conditions by emphasizing full directions with traffic.

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

Usage Guidelines3/5

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

No explicit guidance on when to use vs siblings. The description implies use for full directions, but alternatives like get_traffic_conditions or calculate_distance_matrix are not mentioned. Agent must infer context.

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

Deploy Server