Skip to main content
Glama

Google Maps Places

google_maps_places
Read-onlyIdempotent

Searches Google Maps for local places and businesses and returns up to 20 places (name, address, rating, reviews_count, place_id). Give a location such as "Rome, Italy" or name the place in the query; a search that finds nothing returns NO_DATA and is not charged. It does not return opening hours, phone numbers, review texts or coordinates, and is not web search (use google_search). Required: query.

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>"
    },
    "name": "google_maps_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to find, 1-500 characters, e.g. "pizza" or "pizza in Rome".
resultsNoMaximum places returned, integer 1-20, default 10, e.g. 5.
languageNoTwo-letter language code for names and addresses, e.g. "en" or "it". Omit for the source default, en.
locationNoPlace to centre the search on, as city and country, 1-200 characters, e.g. "Rome, Italy". Without it, a place named in the query ("pizza in Rome") is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Two-letter language code for place results."New value: +"Two-letter language code for names and addresses, e.g. \"en\" or \"it\". Omit for the source default, en."
    • changedInput schema / properties / location / description
      Previous value: -"Place to centre the search on, for example \"Rome, Italy\". Without it, a place named in the query (\"pizza in Rome\") is used."New value: +"Place to centre the search on, as city and country, 1-200 characters, e.g. \"Rome, Italy\". Without it, a place named in the query (\"pizza in Rome\") is used."
    • changedInput schema / properties / query / description
      Previous value: -"Place or business search query."New value: +"What to find, 1-500 characters, e.g. \"pizza\" or \"pizza in Rome\"."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of places to return."New value: +"Maximum places returned, integer 1-20, default 10, e.g. 5."
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world profile, and the description goes beyond them by disclosing the 20-result cap, the exact returned fields, the fields it will NOT return (hours, phone, review texts, coordinates), and that empty searches are not billed. That billing/NO_DATA note is genuinely non-obvious operational context. It doesn't discuss pagination or rate limits, keeping it short of a 5.

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 sentences, front-loaded with purpose, then usage, then exclusions and cost behavior. Every clause carries information an agent needs — returned fields, negative space, and the NO_DATA/uncharged rule — with no filler.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the returned fields and the notable omissions, plus the empty-result signal. For a 4-parameter, fully-documented schema this is sufficient to call correctly without further inspection.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter meaning the schema does not: location is optional because a place named in the query ("pizza in Rome") will be used as the centre. That interplay between query and location is the main semantic risk and is called out explicitly.

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?

Specific verb+resource ("Searches Google Maps for local places and businesses") with the result shape enumerated (name, address, rating, reviews_count, place_id). It explicitly distinguishes itself from the nearest sibling by stating it "is not web search (use google_search)", so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Gives the concrete calling pattern (supply a location like "Rome, Italy" or name the place in the query) and names the alternative for the confusable case (google_search for web results). It also sets the expectation that a zero-result search returns NO_DATA, removing ambiguity about failure handling.

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.

Resources