Google Maps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherC | Gets the current weather. |
| add_postC | Adds a simple text post. |
| get_postsC | Retrieves all posts. |
| delete_postC | Deletes a post by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Three tools (add_post, delete_post, get_posts) clearly relate to a posts/CRUD domain, while get_weather is unrelated to posts and creates a domain mismatch. Within the posts tools, there is good disambiguation (add, delete, get), but the inclusion of weather introduces significant ambiguity about the server's purpose and tool boundaries.
The naming follows a consistent verb_noun pattern (add_post, delete_post, get_posts, get_weather) with clear actions and objects. All tools use snake_case uniformly, making them readable and predictable, though the weather tool's domain deviation slightly affects overall consistency.
With 4 tools, the count is reasonable, but it feels thin for a 'Google Maps MCP Server' as it lacks core mapping functionalities (e.g., geocoding, directions, places search). The tools present cover a basic posts system and weather, which is mismatched with the server name, making the scope unclear and borderline inappropriate.
For a posts domain, the tools provide basic CRUD (add, delete, get) but lack update functionality, creating a minor gap. More critically, for a Google Maps server, there are no mapping-related tools (e.g., search_places, get_directions), resulting in significant gaps that will cause agent failures in handling mapping tasks.