Skip to main content
Glama

Places Search

places_search
Read-onlyIdempotent

Find businesses and points of interest by name and/or category near a point, inside a bbox, or within a city, in the United States and the United Kingdom (Overture Maps places). Returns each place with name, category, confidence score, street address, websites, phones, emails, social links, brand and source record ids, nearest or best match first. Answers "where is the nearest Starbucks to these coordinates", "find dentists in Austin TX", "list Pret A Manger shops in London".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Starbucks",
      "near": {
        "lat": 30.2672,
        "lon": -97.7431
      },
      "limit": 5,
      "radius_m": 3000
    },
    "name": "places_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoBounding box [west, south, east, north] in decimal degrees, as an alternative to near.
cityNoCity / town / locality name, e.g. "Austin" or "London". Needs country.
nameNoBusiness name or words in it, e.g. "Starbucks" or "Pret A Manger". Optional when category is given.
nearNoCentre point {lat, lon} in decimal degrees. Use with radius_m.
limitNoMax places returned (1-200, default 25).
regionNoOptional state or region to disambiguate city, e.g. "TX" or "Texas".
countryNoCountry for city: "US" or "GB" (also accepts "UK", "United States", "United Kingdom").
categoryNoOverture category, e.g. "coffee_shop", "dentist", "hotel", "restaurant", "pharmacy". Matches the basic category, the taxonomy primary or any level of its hierarchy.
radius_mNoSearch radius in metres around near (50-50000).
include_closedNoInclude places Overture marks permanently_closed. Default false.
min_confidenceNoHide places whose Overture existence confidence is below this (0-1). Default 0.7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max places returned (1–200, default 25)."New value: +"Max places returned (1-200, default 25)."
    • changedInput schema / properties / min_confidence / description
      Previous value: -"Hide places whose Overture existence confidence is below this (0–1). Default 0.7."New value: +"Hide places whose Overture existence confidence is below this (0-1). Default 0.7."
    • changedInput schema / properties / radius_m / description
      Previous value: -"Search radius in metres around near (50–50000)."New value: +"Search radius in metres around near (50-50000)."
  2. First observed

TDQS

A3.7/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, so safety is covered; the description still adds real value by disclosing the US/UK coverage limit, the source (Overture Maps), the fields returned, and the result ordering ('nearest or best match first'). It does not mention result caps or failure behavior, keeping it below 5.

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?

Front-loaded with the capability, then return contents, then three concrete example queries that help the agent pattern-match. Dense but each part is useful; the example list is slightly gratuitous at three entries.

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?

For an 11-parameter, no-required, no-output-schema tool, the description covers what it returns, the spatial scoping options, and the country coverage. It leaves unaddressed what happens with an empty parameter set and the city-requires-country coupling that sits only in the schema.

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 every one of the 11 parameters in detail. The description's mapping of name/category to point/bbox/city adds an orientation to which inputs combine, but no syntax, range, or default detail beyond what the schema provides — baseline 3.

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?

States a specific verb and resource ('Find businesses and points of interest') and enumerates the three spatial modes (near a point, inside a bbox, within a city) plus the geographic scope (US/UK, Overture Maps). It does not explicitly differentiate itself from siblings like places_in_area or places_by_domain, so it falls short of a 5.

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 three sample questions ('where is the nearest Starbucks to these coordinates', 'find dentists in Austin TX') imply the intended call patterns, but there is no explicit when-to-use / when-not guidance and no reference to the overlapping sibling tools. Usage is inferable rather than stated.

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.