Skip to main content
Glama
Sign In

Scrappa

by co.scrappa
OverviewDiscussionsAdmin

Search places on Google Maps

google_maps_search_places
Read-onlyIdempotent

Search Google Maps for businesses and places, for example "pizza in Berlin Mitte" or "dentist near Alexanderplatz". Returns public business data: name, rating, number of reviews, category, address, website, phone, coordinates and a business_id. Use the business_id with google_maps_get_reviews to read reviews. Reads public data only.

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_search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of places to return, 1 to 20. Default: 10.
queryYesWhat and where to search, e.g. "pizza in Berlin Mitte".
countryNoTwo-letter country code to focus the search, e.g. "de" or "us".
languageNoTwo-letter language code for the results, e.g. "en" or "de". Default: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond that: it enumerates the returned public fields and clarifies 'Reads public data only', though it says nothing about rate limits or result ordering.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action and examples. The final sentence ('Reads public data only') partially duplicates the readOnlyHint annotation but is brief enough not to be wasteful.

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?

There is no output schema, and the description compensates by listing exactly what fields are returned (name, rating, reviews, category, address, website, phone, coordinates, business_id). Combined with the sibling routing hint, an agent has everything needed to call and follow up correctly.

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 schema already documents all four parameters including the limit range and country/language codes. The description repeats the query example already in the schema and does not add syntax or semantic detail for limit, country, or language.

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 ('Search Google Maps for businesses and places'), gives concrete query examples, and explicitly distinguishes itself from the sibling retrieval tool by routing business_id to google_maps_get_reviews. An agent can identify the tool's function 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 Guidelines4/5

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

Provides example query phrasings ('pizza in Berlin Mitte', 'dentist near Alexanderplatz') and a clear follow-up path via business_id to google_maps_get_reviews. It does not state when to prefer google_search over this tool, so alternatives are only partially addressed.

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

All Scrappa toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources