Skip to main content
Glama

maptiler

by io.usefulapi

Reverse geocode (place at coordinates)

maptiler_reverse_geocode
Read-only

Find the place(s) at a given longitude/latitude, returned as GeoJSON features. API: GET /geocoding/{longitude},{latitude}.json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-10). Default 5.
typesNoComma-separated place types to include.
languageNoComma-separated ISO 639-1 language codes for results.
latitudeYesLatitude, -90..90.
longitudeYesLongitude, -180..180.
worldviewNoDisputed-border worldview: default | auto | ch | us.
excludeTypesNoIf true, `types` becomes an exclude list instead.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true. The description adds that results are GeoJSON features and the API endpoint, but does not disclose other behavioral traits like rate limits, authentication, or error handling.

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 a single, front-loaded sentence plus an API reference. No wasted words.

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?

Given the tool's simplicity, no output schema, and full schema coverage, the description adequately covers what the tool does and its return format. Some additional context about the GeoJSON structure would improve completeness but not required.

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 coverage is 100%, so parameters are fully documented. The description does not add semantics beyond the schema, warranting a baseline score of 3.

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 the action ('Find') and the resource ('place(s) at a given longitude/latitude'), and distinguishes from sibling tools like maptiler_geocode (forward) and maptiler_geolocate_ip.

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?

The description does not explicitly provide usage guidelines, such as when to use this tool versus alternatives like maptiler_geocode. It only implies use when coordinates are known.

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

All maptiler toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: forward geocoding (batch and single), reverse geocoding, IP geolocation, data features retrieval, elevation lookup, coordinate system search, and coordinate transformation. There is no overlap or ambiguity among them.

Naming Consistency4/5

All tools follow a verb_noun pattern with underscores, prefixed by 'maptiler_'. While most are consistent (e.g., 'get_elevation', 'search_coordinate_systems'), 'reverse_geocode' and 'geolocate_ip' are slight variations but still clear. The naming is predictable and readable.

Tool Count5/5

8 tools is an appropriate number for a geolocation and mapping utility server. Each tool serves a distinct operation without being excessive or insufficient. The scope is well-defined.

Completeness4/5

The tool set covers core geolocation operations: forward/reverse geocoding, batch processing, IP geolocation, elevation, coordinate systems, and data features. Minor gaps exist (e.g., no map tile retrieval or routing), but the set is complete for the advertised functionality.

Resources