Skip to main content
Glama

NS Pros MCP Gateway

google-maps__search_places

Call this tool when the user's request is to find places, businesses, addresses, locations, points of interest, or any other Google Maps related search.

Input Requirements (CRITICAL):

  1. text_query (string - MANDATORY): The primary search query. This must clearly define what the user is looking for.

    • Examples: 'restaurants in New York', 'coffee shops near Golden Gate Park', 'SF MoMA', '1600 Amphitheatre Pkwy, Mountain View, CA, USA', `'pets friendly parks in Manh

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": {
      "textQuery": "<textQuery>"
    },
    "name": "google-maps__search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNoOptional. The maximum number of places to return, up to 10. The service may return fewer than this value. The default value is 5. Requesting more than 5 places will trigger the Pro tier and incur higher billing cost and latency.
textQueryYesRequired. The text query.
regionCodeNoOptional. The Unicode country/region code (CLDR) of the location where the request is coming from. This parameter is used to display the place details, like region-specific place name, if available. The parameter can affect results based on applicable law. For example, "US" for United States. For more information, see https://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html. Note that 3-digit region codes are not currently supported.
languageCodeNoOptional. The language to request that the summary is returned in. If the language code is unspecified or unrecognized, the summary with a preference for English will be returned. For example, "en" for English. Current list of supported languages: https://developers.google.com/maps/faq#languagesupport.
locationBiasNoAn optional region to bias the search results to. If an explicit location is in `text_query`, it will be used to bias the search results instead of this field.
includeExtendedDetailsNoOptional. Includes extended place details in the response. Set this field to `true` when the user request requires rich qualitative insights, real-time dynamics, or specialized entity attributes: - Qualitative reviews, customer sentiment, and feedback. - Specific offerings like menu items, dishes, food specialties, beverages, or business highlights. - Qualitative atmosphere, interior decor, aesthetic, ambience, or mood. - Real-time data and specialized facility specs, visitor policies/tips, wait times. Leave `false` (default) for standard discovery searches (e.g., cuisines, store types), location/address lookups, contact info, operating hours, and standard metadata/amenities. Enabling this field will trigger the Pro tier and incur higher billing cost and higher latency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It says nothing about billing tiers, latency, permissions, result caps, or what the response contains — the Pro-tier cost/latency warnings exist only in the schema field descriptions, not here. The text also terminates mid-sentence ('pets friendly parks in Man'), leaving the guidance visibly incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The structure is heavy for the payload: a bolded 'Input Requirements (CRITICAL)' header for a single documented parameter, plus bulleted examples. Worse, the description is truncated mid-example, which is a real defect in a field the agent relies on for routing. The truncation wastes the space where the remaining five parameters should have been addressed.

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?

For a six-parameter search tool with no annotations and no output schema, the description addresses only one parameter and then cuts off. The five optional parameters — pageSize, regionCode, languageCode, locationBias, includeExtendedDetails — are documented only in the schema, and the description never mentions the tiered billing/latency trade-off that materially affects how an agent should set them.

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 the baseline is 3; the description earns an extra point by supplying concrete textQuery examples that show the intended query style — natural-language phrasing with embedded location, addresses, and landmark names. That teaches an agent more about how to formulate the mandatory parameter than the schema's bare 'Required. The text query.' does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource set: 'find places, businesses, addresses, locations, points of interest.' That is clear enough for an agent to know this is the general place-search entry point. It does not distinguish itself from the sibling google-maps__search_along_route, and the catch-all phrase 'any other Google Maps related search' actually blurs the boundary rather than sharpening it.

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?

There is an explicit trigger ('Call this tool when the user's request is to find places...'), which is more than most definitions offer. However, it gives no when-not-to-use guidance and never points to the route-based or name-resolution siblings, so an agent must guess which Maps search tool is appropriate. The overbroad 'any other Google Maps related search' actively discourages the agent from considering alternatives.

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.