The Clearing — The Lantern & Consensual Agent Lab

decode_slippy_tile_coords

Convert Web Mercator Slippy Map tile indices (z, x, y) into WGS84 latitude/longitude and macro-region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "z": "<z>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "decode_slippy_tile_coords"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	Tile column index.
`y`	Yes	Tile row index.
`z`	Yes	Zoom level (0-22).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it omits the most consequential detail: a tile index maps to an extent, not a point, so it is unclear whether the returned lat/lon is the tile's center, NW corner, or another reference. It also says nothing about the coordinate precision or handling of out-of-range zoom values. It does at least disclose the extra macro-region output, which is not derivable from 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.

Conciseness5/5

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

A single front-loaded sentence with no filler; the input tuple and the output both appear before any wasted wording. Nothing could be removed without losing meaning.

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?

The tool is low-complexity and all three parameters are fully documented in the schema, with no output schema to explain. The description names both return values, which compensates for the missing output schema. The residual gap is the unspecified reference point within the tile, which matters for callers needing exact coordinates.

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 description coverage is 100% — each of z, x, and y is documented in the schema (column, row, zoom 0-22). The description only restates the parameter tuple without adding format, ordering, or validity detail beyond what the schema already says, so baseline 3 applies.

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: converting Slippy Map tile indices (z, x, y) into WGS84 lat/lon plus a macro-region. The transformation and both output kinds are named, so an agent knows exactly what it produces. It doesn't differentiate from siblings, but the listed siblings are unrelated utilities, so the marginal cost is small.

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 implies usage — call it when you have tile indices and need geographic coordinates — but never states when to use it, when not to, or what alternative exists for the reverse direction (lat/lon to tile). For a pure conversion utility this is acceptable but leaves the agent to infer the call context.

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

All The Clearing — The Lantern & Consensual Agent Lab tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?