Google Maps

Answer real-world location questions with the package's standalone exec CLI. Do not start or configure an MCP server for this workflow.

Before calling the CLI

• On the first call in a session, or after an execution failure, read ../_shared/setup-and-diagnostics.md and run the non-billable local preflight.
• The user must supply GOOGLE_MAPS_API_KEY. Never print it or place it in a command unless the user explicitly accepts shell-history and process-list exposure.
• Before presenting Places reviews, photos, or AI summaries, read ../_shared/content-attribution.md.

Workflow

1. Identify the concrete location outcome and missing inputs. Do not request details that can be resolved by geocoding or place search.
2. Read references/tools-api.md when exact parameters, response fields, or a multi-tool recipe are needed.
3. Prefer coordinates over ambiguous addresses and place_id over repeated name searches.
4. Chain only the calls needed for the outcome. Reuse returned identifiers and coordinates.
5. Treat nonzero exit status or { "success": false } as a failure, not as geographic data.
6. Summarize the useful result rather than returning raw JSON. Preserve source and attribution metadata where required.