Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

geocoding_lookup

Look up OpenStreetMap objects by comma-separated OSM IDs to retrieve display names, coordinates, bounding boxes, address details, and optional tags.

Instructions

Lookup Nominatim OSM ids. Looks up OpenStreetMap objects by the required osm_ids, a comma-separated list prefixed N (node), W (way) or R (relation), such as W34633854,N123. Each place has its display name, category and type, coordinates, bounding box, importance and address parts; addressdetails defaults to true, and extratags, namedetails and accept_language are optional. Malformed ids return 400; no match returns 404.

Input Schema

NameRequiredDescriptionDefault
osm_idsYesComma-separated OSM ids such as W34633854,N123,R456
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

A3.9/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 burden and does well: it discloses the required input format, that `addressdetails` defaults to true, and the error contract (400 for malformed ids, 404 for no match). It omits rate limits/auth, but the default and error behavior are meaningful beyond the schema.

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?

Front-loaded with the lookup purpose, then id format and examples, then return fields, then error codes. Dense but every sentence contributes; no filler.

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?

With no output schema, the description steps in to enumerate the returned fields (display name, category, type, coordinates, bounding box, importance, address parts) and the failure modes. An agent has everything needed to invoke and interpret the 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 baseline is 3, but the description adds real meaning: it explains the N/W/R prefix semantics and comma-separated syntax for `osm_ids` and confirms which params are optional vs defaulted, information the schema's terse descriptions don't fully 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?

States a specific verb and resource: looks up OpenStreetMap objects by OSM id, and immediately characterizes the input as required `osm_ids`. The id-prefix format (N/W/R) makes it clearly distinct from a text-based geocoder sibling, though it never explicitly names geocoding_search or geocoding_reverse.

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 required id-shaped parameter rather than stated: an agent can infer this is for resolving known OSM ids and not for free-text or coordinate lookups. There is no explicit 'use this instead of X' guidance and no 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