Skip to main content
Glama

Tesela de mapa (XYZ)

map-tile
Read-onlyIdempotent

Convierte lat/lon y zoom a coordenadas de tesela XYZ (Web Mercator) y quadkey, o una tesela a su caja. Cuándo: hay que calcular coordenadas, distancias, rumbos o áreas a partir de puntos dados. No para: codificar latitud/longitud como geohash de precisión 1-12 e informar el tamaño de la celda (geohash-encode). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Converts lat/lon and zoom (0-24) to Web Mercator XYZ tile coordinates and quadkey, or a tile back to its bounding box. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: encoding a latitude/longitude as a geohash string of precision 1-12 and reporting the cell size in metres (geohash-encode). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": 51.5074,
      "lon": -0.1278,
      "zoom": 10
    },
    "name": "map-tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoTile x (to bbox) (integer; optional; min 0).
yNoTile y (to bbox) (integer; optional; min 0).
latNoLatitude (to tile) (number; optional; min -85.05112878; max 85.05112878).
lonNoLongitude (to tile) (number; optional; min -180; max 180).
zoomYesZoom 0-24 (integer; required; min 0; max 24).

Output Schema

NameRequiredDescriptionDefault
xNo
yNo
bboxNo
zoomNo
quadkeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lat": 51.5074,
      +    "lon": -0.1278,
      +    "zoom": 10
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / zoom / examples
      Added value: +[
      +  10
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Converts lat/lon and zoom (0-24) to Web Mercator XYZ tile coordinates and quadkey, or a tile back to its bounding box. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: encoding a latitude/longitude as a geohash string of precision 1-12 and reporting the cell size in metres (geohash-encode). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so 'no side effects, no network, deterministic' only restates them. What does add value is the hard operational envelope — 64 KB input, 1 s per call and 1 MB result — which the annotations do not provide and which the agent cannot infer from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is front-loaded and each fact is tagged, but the same text is given in both Spanish and English, and the schema.description field repeats it verbatim. The trailing pointer '[EN completo / full EN: inputSchema.description]' is meta clutter that adds no information for the caller.

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?

Because the output schema exists, the description does not need to explain the return values. It does cover both invocation modes, the exclusion against geohash-encode, the cost and size limits, and the deterministic contract. The only shortfall is that it does not say which parameter combinations are valid for each mode, although the 'lat/lon to tile' and 'tile to bbox' phrasing implies this reasonably well.

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?

The schema coverage is 100%, but the schema also presents all five parameters as optional reads with no mode switch, so the description's key contribution is defining the two directions — converting lat/lon plus zoom into tile coordinates, and converting x/y plus zoom into a bounding box — which is not obvious from the flat property list. It also restates the zoom range of 0–24, and that restatement is redundant, but the mode selection is genuine added meaning.

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 opening sentence names a specific verb and resource: it converts lat/lon plus zoom into Web Mercator XYZ tile coordinates and a quadkey, and it can also convert a tile back into its bounding box. It also names a sibling tool, geohash-encode, as the tool this one is not, so an agent can distinguish the two without opening either schema.

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 gives an explicit "Cuándo" block and a "No para" exclusion that names the alternative geohash-encode, which is good structure. However, the stated use case — 'coordinates, distances, bearings or areas have to be computed' — is misleading, because distances and bearings belong to siblings such as geo-haversine, geo-bearing and geo-polygon-area; the text also fails to mention other look-alikes, such as utm-from-latlon, plus-code-encode or geo-bounding-box.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources