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

google-maps-mcp-server

by ettysekhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_places

Search for nearby places using location and keywords. Retrieve names, addresses, ratings, and other details.

Instructions

Search for nearby places based on location and keywords. Returns place names, addresses, ratings, and other details.

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": {
      "location": "<location>",
      "keyword": "<keyword>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesLocation as 'lat,lng' (e.g., '37.7749,-122.4194')
keywordYesKeyword to search for (e.g., 'gas station', 'restaurant')
radiusNoSearch radius in meters (default: 5000, max: 50000)
typeNoPlace type (e.g., 'restaurant', 'gas_station', 'parking')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the tool searches and returns data, but omits details like authentication requirements, rate limits, error handling, or the fact that results may be limited. The description is sufficient for a simple search but lacks depth.

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?

The description consists of two short sentences that convey the purpose and output without any fluff. Every word serves a purpose, making it highly concise and well-structured.

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?

Given the tool has no output schema, the description compensates by listing the types of data returned (names, addresses, ratings, etc.). However, it does not mention result limits, pagination, or how to interpret the 'other details'. Still, it provides sufficient context for a search tool.

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 coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond what the schema already provides (e.g., 'based on location and keywords' is a paraphrase). It does not explain how parameters interact or provide examples.

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 tool searches for nearby places based on location and keywords, and it lists the type of data returned. This distinguishes it from sibling tools like get_place_details (which retrieves details for a specific place) and geocode_address (which converts addresses to coordinates).

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?

The description implies when to use (searching for places by location and keywords) but provides no explicit guidance on when not to use it or when to prefer a sibling tool like get_place_details or reverse_geocode. No alternatives are mentioned.

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