@cablate/mcp-google-map 0.0.26 → 0.0.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/google-maps/SKILL.md +12 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cablate/mcp-google-map",
3
- "version": "0.0.26",
3
+ "version": "0.0.27",
4
4
  "mcpName": "io.github.cablate/google-map",
5
5
  "description": "Google Maps tools for AI agents — 8 tools (geocode, search, directions, elevation) via MCP server or standalone Agent Skill CLI",
6
6
  "type": "module",
package/skills/google-maps/SKILL.md CHANGED
@@ -1,6 +1,14 @@
1
1
  ---
2
2
  name: google-maps
3
3
  description: Geospatial query capabilities — geocoding, nearby search, routing, place details, elevation. Trigger when the user mentions locations, addresses, coordinates, navigation, "what's nearby", "how to get there", distance/duration, or any question that inherently involves geographic information — even if they don't explicitly say "map". Update when new tools are added or tool parameters change.
4
+ license: MIT
5
+ version: 0.0.25
6
+ compatibility:
7
+ - claude-code
8
+ - cursor
9
+ - vscode-copilot
10
+ - openai-codex
11
+ - gemini-cli
4
12
  ---
5
13
 
6
14
  # Google Maps - Geospatial Query Capabilities
@@ -17,9 +25,11 @@ Without this Skill, the agent can only guess or refuse when asked "how do I get
17
25
 
18
26
  | Principle | Explanation |
19
27
  |-----------|-------------|
20
- | Chain over single-shot | Most geo questions require chaining: geocode → search-nearby → place-details. Think about the full pipeline when planning queries. |
28
+ | Chain over single-shot | Most geo questions require 2-5 tool calls chained together. See Scenario Recipes in references/tools-api.md for the full patterns. |
29
+ | Match recipe to intent | Map the user's question to a recipe (Trip Planning, Local Discovery, Route Comparison, Neighborhood Analysis, Multi-Stop, Place Comparison, Along the Route) before calling any tool. |
21
30
  | Precise input saves trouble | Use coordinates over address strings when available. Use place_id over name search. More precise input = more reliable output. |
22
31
  | Output is structured | Every tool returns JSON. Use it directly for downstream computation or comparison — no extra parsing needed. |
32
+ | Present as tables | Users prefer comparison tables and scorecards over raw JSON. Format results for readability. |
23
33
 
24
34
  ---
25
35
 
@@ -75,4 +85,4 @@ npx @cablate/mcp-google-map exec <tool> '<json_params>' [-k API_KEY]
75
85
 
76
86
  | File | Content | When to read |
77
87
  |------|---------|--------------|
78
- | `references/tools-api.md` | Full parameter specs, response formats, and chaining patterns for all 8 tools | When you need exact parameter names, types, response shapes, or multi-tool workflows |
88
+ | `references/tools-api.md` | Full parameter specs, response formats, 7 scenario recipes, and decision guide | When you need exact parameters, response shapes, or multi-tool workflow patterns |