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

google-maps-mcp-server

by ettysekhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

geocode_address

Convert a street address into precise geographic coordinates (latitude/longitude) to enable location-based queries and mapping.

Instructions

Convert a street address to geographic coordinates (latitude/longitude).

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": {
      "address": "<address>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesStreet address to geocode
componentsNoComponent filters (e.g., {'country': 'US'})
regionNoRegion bias (ISO 3166-1 country code)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations are absent, so the description must disclose behavioral traits. It does not mention what happens on failure, whether multiple results are returned, or any necessary authorization. The schema includes parameters like 'components' and 'region' but their behavioral impact is not explained.

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?

Single sentence is front-loaded and contains no redundant information. Every word earns its place. Highly concise.

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

Completeness2/5

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

No output schema is provided, so the description should hint at return format. It only says 'latitude/longitude' without specifying whether it returns a single point, a list, or additional metadata. For a geocoding tool with 3 parameters (one nested), this is insufficiently complete.

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

Parameters2/5

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

Schema coverage is 100%, so the schema descriptions already document each parameter. The tool description adds no additional meaning beyond the schema, e.g., it merely restates 'address', 'components', and 'region' without elaborating on format constraints or usage nuances.

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 the action ('Convert a street address to geographic coordinates') and the resource ('street address'). It is specific and distinguishes from siblings like 'reverse_geocode' which does the opposite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as 'get_place_details' or 'search_places'. No mention of context, prerequisites, or exclusions. The description implies usage but does not help an agent decide between siblings.

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