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

google-maps-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Maps Status

maps_status
Read-onlyIdempotent

Checks Google Maps service health and shows remaining request and tile budgets, breaker state, last error, cache size, and optional live route, place, and tile canary results.

Instructions

Version, daily request and tile budgets left, breaker, last error and cache size. With check=true, also {canary: {ok, code, checked_at, cached}}: one real route, one place read and one map tile, cached 55 min (5 min after a transient failure); ok is false on any error. Never fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maps_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNoAlso run the live canary (cached 55 min)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains the canary payload, the 55-minute cache, the shorter 5-minute cache after a transient failure, the meaning of ok, and the strong 'Never fails' guarantee. These details materially help an agent understand how the tool behaves.

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 compact and front-loaded, listing the core status fields first and then explaining the optional canary mode. Every sentence carries useful information, with no boilerplate.

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

Completeness5/5

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

Given that an output schema exists, the description need not document return values in full. It still provides enough context about status fields, canary behavior, caching, and failure semantics for an agent to call the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for check=true: it specifies the canary result shape and that it performs one real route, one place read, and one map tile with caching behavior. This goes beyond the schema's brief parameter note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the status/diagnostic resource it exposes: version, daily request and tile budgets, breaker, last error, and cache size. It is not a tautology, but it does not explicitly differentiate itself from the maps_* action siblings beyond the inherently different status content.

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?

Usage is implied: this is a health/quota-status tool, and 'With check=true' explains the conditional live-canary mode. However, there is no explicit guidance on when to call it versus other tools, nor when to avoid it.

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