Skip to main content
Glama
Sign In
google-maps-mcp-server

google-maps-mcp-server

by ettysekhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_route_elevation_gain

Calculate elevation gain and retrieve elevation profile for any route. Ideal for planning cycling, hiking, or optimizing fuel efficiency.

Instructions

Calculate elevation gain and retrieve elevation profile for a route. Useful for cycling, hiking, or fuel efficiency analysis.

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_route_elevation_gain"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesStarting location (address or 'lat,lng')
destinationYesEnding location (address or 'lat,lng')
modeNoTravel mode (elevation is most relevant for bicycling/walking)bicycling
samplesNoNumber of elevation samples along the route (max 512)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states basic function without disclosing behavioral traits like data source, precision, rate limits, or behavior when route lacks elevation data. Incomplete for a calculation tool.

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?

Two concise sentences: first defines function, second gives use cases. No wasted words, immediately readable.

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 simple tool, but lacks details on output format, error handling, and parameter effects. No output schema means description should clarify return values. Could be improved.

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 baseline is 3. Description adds minimal value beyond schema, only generic use-case context. Does not enhance parameter understanding (e.g., sample impact or mode differences).

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 the tool calculates elevation gain and retrieves elevation profile for a route, with specific use cases (cycling, hiking, fuel efficiency). It uniquely addresses elevation among siblings like calculate_distance_matrix or get_directions.

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?

Provides implicit context by mentioning 'cycling, hiking, or fuel efficiency' but lacks explicit guidance on when to use this tool versus alternatives (e.g., for distance use calculate_distance_matrix). No exclusions or when-not-to-use mentioned.

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

Deploy Server

Other Tools