Skip to main content
Glama

maptiler

by io.usefulapi

Transform coordinates between CRS

maptiler_transform_coordinates
Read-only

Transform up to 50 coordinate pairs from a source coordinate reference system to a target one (EPSG codes). API: GET /coordinates/transform/{coordinates}.json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsNoPipe-separated transformation operation codes to force a path.
s_srsNoSource CRS / EPSG code. Default 4326 (WGS84).
t_srsNoTarget CRS / EPSG code. Default 4326 (WGS84).
coordinatesYes1-50 [x, y] coordinate pairs in the source CRS.

Schema Changelog

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

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description does not contradict (transformation is read-like). Adds constraints (max 50, EPSG codes) and API endpoint. No missing behavioral traits.

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 efficient sentences, no fluff, key information front-loaded. Every word adds value.

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?

For a transformation tool without output schema, description covers inputs, constraints, and API. Missing description of output format, but not critical for agent invocation.

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 baseline is 3. Description adds the 50-pair limit and API path, but these are already implied by schema min/max. Minimal additional semantic value.

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?

Clearly states the verb 'transform', resource 'coordinate pairs between CRS', constraints 'up to 50' and 'EPSG codes'. Distinguishes from sibling geocoding/elevation tools.

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?

Implies usage for coordinate transformation but does not explicitly state when to use this vs alternatives like maptiler_search_coordinate_systems or when not to use it.

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