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 nearby place name and address details using Nominatim JSONv2. Provide coordinates to retrieve location context for mapping or geolocation tasks.

Instructions

Reverse geocode coordinates. Returns the nearest typed Nominatim JSONv2 place for latitude and longitude.

Input Schema

TableJSON 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

B3.3/5.0
Behavior2/5

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

With no annotations, the description bears full burden for behavioral disclosure. It does not mention potential errors, rate limits, authentication requirements, or whether the result is always a single place. The phrase 'nearest typed' is vague.

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?

Two concise sentences with no redundant information. The purpose and return format are front-loaded.

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?

The description provides a high-level overview but lacks details on optional parameter usage, return structure, and edge cases. Given 7 parameters and no output schema, more guidance would improve completeness.

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?

All 7 parameters have explicit descriptions in the schema (100% coverage), so the description does not need to add much. However, the description provides no additional context on how parameters like zoom or addressdetails affect the result.

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 clearly states it performs reverse geocoding, converting coordinates to a place. It specifies the output format (Nominatim JSONv2) and distinguishes itself from forward geocoding tools like geocoding_search.

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?

No explicit guidance on when to use this tool versus alternatives like geocoding_search or geocoding_lookup. The description does not mention prerequisites, context, or exclusions.

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