Skip to main content
Glama

google: Google Maps place search

google_mapsSearch
Read-only

Google Maps place search. Business listings near a coordinate: name, address, phone, website, rating and hours, 20 per page. A failed attempt returns upstream_unavailable and is not charged. Costs 5 credits.

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": {
      "query": "<query>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "google_mapsSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoTwo-letter country code Google should bias results toward.
hlNoHost language for the results page, e.g. "en", "de". Defaults to "en".en
tldNoGoogle marketplace TLD. One of: com, co.uk, ca, de, es, fr, it, co.jp, in, cn, com.sg, com.mx, ae, com.br, nl, com.au, com.tr, sa, se, pl. Defaults to "com".com
uuleNoNot currently supported; any value returns `invalid_request`.
queryYesSearch query
startNo0-based result offset.
latitudeYesLatitude of the search centre
longitudeYesLongitude of the search centre
country_codeNoTwo-letter country code. Sets `gl` when `gl` is not given.
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / uule / description
      Previous value: -"Encoded Google location string for precise geo-targeting."New value: +"Not currently supported; any value returns `invalid_request`."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds materially more: page size (20 per page), a documented failure mode (`upstream_unavailable`), the fact that failed attempts are not charged, and a 5-credit cost. That is exactly the billing/error context an agent needs before spending credits. It stops short of 5 because it says nothing about caching behavior or how `cache_max_age` affects cost/freshness.

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?

Three short sentences, zero filler, with the resource identity and the return fields front-loaded and cost/error behavior last. Every sentence carries distinct, actionable information.

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

Completeness4/5

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

With 10 parameters, no output schema, and a paid open-world call, the description does the important work: it names the returned fields (compensating for the absent output schema), states page size for pagination reasoning, and covers error and billing behavior. The remaining gap is guidance on the caching parameter and on when a coordinate-based lookup is preferable to a general search.

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

Parameters3/5

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

Schema description coverage is 90%, so the schema already explains gl, hl, tld, start, and the coordinate params — baseline 3. The description only reinforces that the coordinate is a 'search centre' and that results page at 20 per call, which nudges the agent toward `start` for pagination but adds no syntax or constraint detail beyond the schema.

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?

States a specific verb and resource ('Google Maps place search') and immediately narrows it to 'business listings near a coordinate', which cleanly separates it from web-oriented siblings such as google_search, google_news, or google_jobs. It even enumerates the returned fields (name, address, phone, website, rating, hours), so an agent knows exactly what class of result it gets.

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 by the required coordinate plus query shape — an agent can infer 'use this for local business lookups' — but there is no explicit when-to-use/when-not or named alternative (e.g. versus google_search or google_shopping) for ambiguous local-intent queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.