Skip to main content
Glama

Places In Area

places_in_area
Read-onlyIdempotent

Count and list the businesses and points of interest inside an area, a bbox, a radius around a point, or a whole city, in the United States and the United Kingdom (Overture Maps places), optionally for one category. Returns the total, a breakdown by category, and the highest-confidence places. Answers "how many restaurants are in this bbox", "what kinds of businesses are within 500 m of this address", "how many gyms are in Manchester".

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": {
      "near": {
        "lat": 51.5072,
        "lon": -0.1276
      },
      "limit": 5,
      "category": "coffee_shop",
      "radius_m": 500
    },
    "name": "places_in_area"
  }
}

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.
nearNoCentre point {lat, lon} in decimal degrees. Use with radius_m.
limitNoMax places listed (0-200, default 25). Counts cover the whole area.
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 listed (0–200, default 25). Counts cover the whole area."New value: +"Max places listed (0-200, default 25). Counts cover the whole area."
    • 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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds genuine behavior context instead — that returned data is Overture Maps places from the US and UK only, and that the response includes a total, a category breakdown and highest-confidence places. It also clarifies the important scoping rule that counts cover the whole area even though listing is limited, which is the kind of nuance annotations cannot express.

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?

Two sentences, heavily front-loaded with the capability statement, followed by the return shape and then illustrative queries. The three verbatim question examples are the only borderline padding, but they do useful disambiguation work rather than repeating the opening sentence.

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?

With ten parameters, zero required fields and no output schema, an agent would normally be guessing; the description compensates by describing the return payload (total, category breakdown, top-confidence places) and the data provider. Combined with full schema coverage of every parameter's constraints, an agent has what it needs to construct a call 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 every one of the ten parameters (bbox format, near/radius_m pairing, country requirement for city, limit range, category taxonomy matching, min_confidence default) is already documented in the schema. The description adds only the framing that category filtering is optional and that counts are area-wide, which is largely a restatement of the limit parameter's own text.

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 pair ('count and list') and a specific resource ('businesses and points of interest'), plus the spatial modes (bbox, radius, city) and geography (US/UK, Overture Maps). It never names or contrasts with places_search or places_by_domain, so sibling differentiation is left to the reader despite the underlying data source being the same.

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?

The three quoted example questions ('how many restaurants are in this bbox', 'what kinds of businesses are within 500 m', 'how many gyms are in Manchester') give clear, concrete conditions for when this tool fits, especially the counting/breakdown framing. There is no explicit when-not guidance or named alternative for scenarios where the agent wants ranked search results rather than aggregate counts.

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.