Skip to main content
Glama

osm_search_poi

Read-onlyIdempotent

Find nearby points of interest like restaurants, cafes, or pharmacies in Dubai by specifying latitude, longitude, and category. Returns up to 25 results within a 1 km radius.

Instructions

Find OpenStreetMap points of interest near a Dubai location.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "category": "<category>"
    },
    "name": "osm_search_poi"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return.
categoryYesOne of: restaurant, cafe, fast_food, pharmacy, hospital, clinic, atm, bank, fuel, school, kindergarten, mosque, supermarket, mall, bus_stop, metro_station, parking, park, gym, hotel, embassy, post_office.
latitudeYesCentre latitude.
longitudeYesCentre longitude.
radius_metersNoSearch radius in metres (max 10000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety semantics are covered. The description adds the meaningful coverage constraint that results are Dubai-scoped OSM data, but says nothing about data freshness, rate limits, or empty-result behavior for an open-world lookup.

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?

One efficiently front-loaded sentence with no filler or redundant clauses. It is arguably too terse for a tool with a 22-value category constraint, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% parameter coverage, the description needn't explain return values. However, for a moderately complex geospatial lookup it omits useful context: the OSM/Overpass data source, the Dubai-only geographic restriction, and the relationship to osm_list_categories for valid category values.

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 latitude, longitude, category, radius_meters and limit are all documented in the schema. The description adds no parameter detail (e.g. how category relates to osm_list_categories, or the 10 km radius cap), so the baseline 3 applies.

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?

Clear verb ('Find') plus specific resource ('OpenStreetMap points of interest') and a scope constraint ('near a Dubai location'). An agent understands the operation immediately, but the description never distinguishes it from the related osm_list_categories sibling or from other location tools like makani_reverse_geocode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The phrase 'near a Dubai location' implies a coordinate-based proximity search, but there is no explicit when-to-use statement, no when-not-to-use, and no pointer to alternatives. An agent wanting to discover valid categories has no hint that osm_list_categories exists for that purpose.

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

Deploy Server

Other Tools