Skip to main content
Glama

Search nearby pharmacies, cafes and other places

places
Read-only

Points of interest near a point (lat and lon, or a place name geocoded through OpenStreetMap) within up to 5 km: pharmacies, restaurants, cafes, hospitals, ATMs, banks, fuel, EV charging, hotels, supermarkets, parking, schools, police, toilets. Name, distance, address parts, opening hours, phone and website when tagged. OpenStreetMap data (ODbL). Up to 50 results. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "category": "<category>"
    },
    "name": "places"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (with lon)
lonNoLongitude (with lat)
limitNoPlaces to return, 1 to 50, default 20
placeNoPlace name, geocoded (instead of lat and lon)
radiusNoRadius in metres, 50 to 5000, default 1000
categoryYesrestaurant, cafe, pharmacy, hospital, atm, bank, fuel, ev_charging, hotel, supermarket, parking, school, police or toilets

Output Schema

NameRequiredDescriptionDefault
countNo
pointNo
placesNo
sourceNo
radiusMNo
categoryNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses the cost model ($0.002 per successful call via x402/USDC across multiple networks), that failed calls are free, the 50-result cap, and the data source/licence (OpenStreetMap, ODbL). It also previews returned fields (distance, address parts, opening hours, phone, website), so an agent knows what it gets and what it pays.

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?

The scope, coverage radius and output fields are front-loaded in the opening clause, with pricing separated into a second sentence. The enumerated category list duplicates the schema's category description and adds some bulk, but nothing is genuinely off-topic.

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?

For a read-only, open-world lookup with a full schema and output schema, the description covers the remaining unknowns: cost, charging conditions, result ceiling, spatial limit and source data. An agent has everything needed to decide and 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 the baseline is 3. The description largely restates schema facts (geocoding of the place name, the 50-result and 5 km limits) rather than adding format or syntax detail beyond them, e.g. expected coordinate string format or whether partial results are returned when nothing matches.

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 states a specific resource and scope: points of interest near a coordinate or place name, with an explicit category list and radius cap. The resource is unambiguously distinct from siblings like distance, airports or address_parse. It does not name any sibling to route against, so it stops 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 Guidelines4/5

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

It makes the two input modes explicit ('lat and lon, or a place name geocoded through OpenStreetMap') and states the 5 km operating range, which is enough context to choose inputs correctly. There is no when-not guidance or named alternative for pure geocoding/distance queries.

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.

Resources