Skip to main content
Glama

Nearby Mapped Places

get_nearby_mapped_places
Read-onlyIdempotent

Purpose: find mapped nearby schools, shops and services worldwide. When to use: compare local place context around a known site, or prepare mapped points for QGIS. Returns: selected OpenStreetMap point categories from fixed regional sources, straight-line distances in metres, per-layer coverage, source references, an inspectable map and GeoJSON. Limitations: community mapping, not official access evidence or a complete inventory; source freshness, entrances, opening hours and public/wheelchair access are unverified. No walking routes, travel times, parks, bus stops, rail stations or transit frequency; do not infer a walk score or 15-minute-city verdict. Parameter guidance: supply address with country, a prior site_ref, or WGS84 coordinates {lat,lng} with explicit country_code. Non-UK address lookup requires the configured service. Persona selects default category groups; explicit categories can request only mapped schools, hospitals or other supported point types. Radius is 250 to 1000 metres. Missing data means unknown, never absence of services. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_nearby_mapped_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoSite address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations.
personaNo
site_refNoCanonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted.
categoriesNoOptional explicit mapped categories, for example school or hospital. Overrides persona defaults; not complete nearest-place coverage.
coordinatesNoUser-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified.
country_codeNoISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK.
radius_metersNoSearch radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected.

Output Schema

NameRequiredDescriptionDefault
queryNo
statusYes
detailsNo
messageNo
sourcesYes
headlineYes
site_refYes
retryableNo
error_codeNo
atlasly_linkYes
error_sourceNo
human_messageNo
key_data_pointsYes
top_constraintsYes
confidence_notesYes
executive_summaryYes
next_best_actionsYes
top_opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Site address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations."
    • addedInput schema / properties / coordinates / description
      Added value: +"User-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified."
    • addedInput schema / properties / country_code / description
      Added value: +"ISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK."
    • addedInput schema / properties / radius_meters / description
      Added value: +"Search radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds material context: data is community-mapped, source freshness/entrances/opening hours/access are unverified, and missing data means unknown rather than absence of services. It also discloses the account-tier radius cap and that non-UK address lookup depends on a configured service. The minor tension between 'radius is 250 to 1000 metres' and the schema's mention of 2000 m for account holders keeps this from a 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?

Long, but organized into labeled sections (Purpose, When to use, Returns, Limitations, Parameter guidance, Chaining) with the core purpose front-loaded. Dense rather than padded, though a few limitations could be compressed without loss.

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?

Covers intent, exclusions, return contents, and cross-tool chaining for a 7-parameter tool with nested site_ref — an agent has enough to call it correctly, and the output schema relieves the description of enumerating return fields. The lone gap is the slight internal ambiguity about maximum radius versus the schema's account-tier note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (86%), so the baseline is 3; the description earns above that by explaining what the schema leaves implicit — that persona drives default category groups while explicit categories override them, that addresses outside the UK need a country, and that coordinates must be paired with country_code. The persona parameter in particular has an enum but no schema description, and this text supplies its meaning.

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?

States a specific verb and resource ('find mapped nearby schools, shops and services worldwide') and bounds the scope to OpenStreetMap point categories, which separates it from analysis-oriented siblings like analyze_site or get_location_coverage. The QGIS-prep framing further pins down the output type an agent should expect.

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?

Has an explicit 'When to use' clause plus an unusually strong exclusion list ('No walking routes, travel times, parks, bus stops, rail stations… do not infer a walk score or 15-minute-city verdict'), which actively steers the agent away from misuse. The chaining sentence ('every response returns site_ref; pass it unchanged into another Atlasly tool') also tells the agent where this tool sits in a multi-call flow.

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