Skip to main content
Glama
Ocean-Ch

google-maps-transit

by Ocean-Ch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_places

search_places
Read-only

Search real-time Google Maps data to find restaurants, hotels, parks, and shops by name, type, or area. Filter results by open status to plan trips or locate nearby services.

Instructions

Searches for places — restaurants, cafés, hotels, attractions, shops, parks, and more — using real-time Google Maps data.

        Use this when the user asks things like:
        • "Find coffee shops near the Eiffel Tower"
        • "Best sushi restaurants in downtown Seattle"
        • "Dog-friendly parks in Austin, TX"
        • "Museums open right now in London"
        • "Gas stations along Highway 1"

        Returns up to 20 results with name, address, star rating, price level, open/closed status, and type tags.
        To get phone number, website, opening hours, and user reviews for a specific result, pass its id to get_place_details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nearNoOptional location context appended to the query, e.g. 'Golden Gate Bridge, San Francisco' or 'Paris, France'. Use this to bias results toward a specific area.
typeNoOptional Google Place type filter. Common values: restaurant, cafe, bar, bakery, hotel, lodging, tourist_attraction, museum, art_gallery, park, zoo, amusement_park, shopping_mall, grocery_or_supermarket, gas_station, hospital, pharmacy, gym, movie_theater, night_club, library. See Google Place Types for the full list.
queryYesWhat to search for, e.g. 'coffee shop', 'Italian restaurant', 'museum', 'dog-friendly park'.
open_nowNoIf true, only return places that are currently open.
max_resultsNoMaximum number of results to return (1–20). Default: 10.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
placesYes
query_usedYesThe final text query sent to the Places API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context beyond that: real-time Google Maps data, a maximum of 20 returned results, the result fields provided, and the handoff condition to get_place_details. It does not cover rate limits or auth requirements, so it is strong but not exhaustive.

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 is front-loaded with the core action, then immediately gives concrete trigger examples, then summarizes output and the routing alternative. Every section is useful and there is 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?

An output schema exists, so the description does not need to explain return values in full, yet it still summarizes the result shape and the detail-retrieval follow-up. For a read-only discovery tool with complete parameter documentation, nothing essential is missing.

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 100%, so the baseline is 3. The description provides example query strings and notes the return count, but it does not materially extend the meaning of near, type, open_now, or max_results beyond what the schema already documents.

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 states a specific verb and resource ('Searches for places') and enumerates the kinds of places covered. It clearly distinguishes this discovery tool from the sibling get_place_details by explaining that details require passing a result id to that sibling.

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?

It gives explicit example user queries that should trigger this tool, says when to use it, and points to get_place_details for deeper information about a specific result. The when-to-use and alternative routing are both explicit.

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