Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

geocoding_reverse

Convert latitude and longitude coordinates into the nearest OpenStreetMap place, including address, category, and type details.

Instructions

Reverse geocode coordinates. Returns the nearest OpenStreetMap place for the required lat and lon. zoom (0 to 18, default 18) sets the level of detail; addressdetails defaults to true, and extratags, namedetails and accept_language are optional. The place has its display name, category and type, OSM type and id, bounding box, importance and address parts. Out-of-range coordinates return 400; no place found returns 404.

Input Schema

NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
zoomNoNominatim address zoom, defaults to 18
extratagsNoInclude OSM extra tags
namedetailsNoInclude multilingual name details
addressdetailsNoInclude address details, defaults to true
accept_languageNoPreferred result language, forwarded to Nominatim

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it states defaults (zoom=18, addressdetails=true), the optional flags, and specific error behavior (400 for out-of-range coordinates, 404 when no place is found). It omits rate-limit/auth context, so it stops short of 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.

Conciseness5/5

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

Front-loaded with the core operation, then defaults, output contents and error codes in tight sequence. Every sentence contributes; nothing is redundant.

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?

No annotations and no output schema, so the description must cover everything. It does: purpose, required/optional parameters with defaults, the fields returned in the place object, and error codes, which is complete for a 7-parameter geocoding call.

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 100%, so the baseline is 3. The description adds genuine value beyond the schema by giving the zoom range (0 to 18) and confirming which parameters are optional, details the schema descriptions only partially convey.

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 verb and resource ('Reverse geocode coordinates') and clarifies scope ('Returns the nearest OpenStreetMap place for the required lat and lon'). The 'reverse' qualifier implicitly separates it from forward-geocoding siblings, but no sibling tool is named explicitly, so it falls 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 Guidelines3/5

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

Usage is implied by the operation itself: you call this when you hold coordinates and want a place. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives such as geocoding_search or geocoding_lookup, leaving the agent to infer routing.

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