geospatial-mcp

Overview Schema Source Related Servers Discussions Admin

place_search

Read-onlyIdempotent

Find nearby points of interest by category using OpenStreetMap. Results are distance-sorted with bearing from the search center, useful for locating fuel, hospitals, EV chargers, and other facilities.

Instructions

Find points of interest of a given category near a location.

Searches OpenStreetMap for facilities by type -- fuel stations along a route, hospitals near an incident, EV chargers in a city, warehouses in a catchment, communication towers on a ridge. Results are sorted by distance and include the bearing from the search centre.

For one specific named place, use place_geocode instead.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results.
`category`	Yes	What to look for. One of: fuel, ev_charging, parking, hospital, pharmacy, clinic, police, fire_station, school, restaurant, cafe, hotel, supermarket, bank, atm, toilets, drinking_water, bus_stop, railway_station, airport, port, warehouse, power_substation, power_tower, communication_tower, water_tower, viewpoint, shelter, campsite, peak, bridge, farmland.
`location`	Yes	Centre of the search, as coordinates or a place name.
`radius_m`	No	Search radius in metres.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`count`	Yes
`centre`	Yes
`places`	Yes
`category`	Yes
`radius_m`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already carry readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral details beyond annotations: it searches OpenStreetMap, results are sorted by distance, and results include bearing from the search centre.

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

Conciseness5/5

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

The description is compact and front-loaded, beginning with a clear one-sentence summary, followed by concrete use examples, then an explicit pointer to the alternative tool. Every sentence contributes useful information without redundancy.

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?

The description is complete for this tool: it explains what the tool searches, the types of results returned, the sorting and bearing behavior, and when to use a sibling tool instead. With a rich input schema, an output schema present, and thorough annotations, nothing essential is missing.

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 fully documents all parameters with defaults and constraints. The description adds contextual examples of category values, but it does not provide meaningful parameter format or semantics details beyond what the schema already states.

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?

The description states a specific verb and resource: 'Find points of interest of a given category near a location' and elaborates with concrete examples and 'Searches OpenStreetMap for facilities by type.' It clearly differentiates from place_geocode by noting that the geocoder is for a single named place.

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

Usage Guidelines5/5

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

The description gives explicit use cases such as fuel stations along a route, hospitals near an incident, and EV chargers in a city. It also names the alternative tool, place_geocode, and specifies the condition under which that alternative should be used instead: 'For one specific named place.'

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