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

google-maps-mcp-server

by ettysekhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_speed_limits

Get speed limit data for road segments by providing place IDs from snap_to_roads. Used for fleet safety and compliance monitoring.

Instructions

Get speed limit data for road segments. Requires place IDs from snap_to_roads. Critical for fleet safety and compliance monitoring.

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": {
      "place_ids": "<place_ids>"
    },
    "name": "get_speed_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
place_idsYesPlace IDs from snap_to_roads results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as rate limits, error conditions, data format (e.g., units of speed), or whether the tool is idempotent. The mention of 'critical for fleet safety' provides importance but no behavioral specifics.

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?

The description is two efficient sentences: first states the core purpose and input requirement, second adds context. No redundant words or fluff.

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?

The description provides basic information but lacks details about return values (e.g., speed limit format, units, data structure) which would be helpful since there is no output schema. It is adequate for a simple tool but could be more complete for safety-critical use.

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% and already explains the parameter as 'Place IDs from snap_to_roads results'. The description adds 'from snap_to_roads' which is redundant with the schema. No additional semantic value beyond the schema, so 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 clearly states 'Get speed limit data for road segments' with a specific verb and resource. It distinguishes from siblings by specifying the prerequisite input (place IDs from snap_to_roads), which is unique among the listed sibling tools.

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?

The description explicitly states 'Requires place IDs from snap_to_roads', giving clear context on when to use this tool (after snap_to_roads). It does not explicitly mention when not to use or list alternatives, but the prerequisite guidance is strong.

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