Skip to main content
Glama

Reverse geocode coordinates to an address

reverse_geocode
Read-only

Resolve WGS84 coordinates to a registered Swiss building/address using GWR data, returning street, number, postal code, locality, municipality and EGID.

Instructions

Find the nearest registered building/address for WGS84 coordinates using the federal Register of Buildings and Dwellings (GWR). Returns street, number, postal code, locality, municipality and EGID.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland: ~45.8–47.9)
lonYesWGS84 longitude (Switzerland: ~5.9–10.6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that — the authoritative source (federal Register of Buildings and Dwellings) and the returned attributes (street, number, postal code, locality, municipality, EGID) — but says nothing about behavior when no building is registered nearby, nor about error handling for out-of-country coordinates.

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?

Two short sentences with no filler; the operation and data source are front-loaded before the return fields. The second sentence is a compact enumeration of outputs, justified by the absence of an output schema, though it reads slightly list-like.

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 two-parameter read-only lookup with a fully documented schema and no output schema, the definition covers purpose, data source, and return fields adequately. The main gap is unstated behavior for coordinates outside Switzerland or locations without a registered building, which matters because the bounds are narrower than the country itself.

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%, and both parameters carry bounds plus Swiss range hints, so the schema does the heavy lifting. The description only restates 'WGS84 coordinates' without adding format, precision, or interpretation guidance, which is the expected baseline when the schema is complete.

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?

The description gives a specific verb and resource ('Find the nearest registered building/address for WGS84 coordinates') and names the underlying dataset (GWR), so an agent knows exactly what operation this is. It does not explicitly contrast itself with the sibling 'geocode' tool, which is presumably the forward direction, leaving that differentiation to the agent's inference from the name.

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 only implied: the tool is for turning coordinates into an address, and the name plus description make that readable. There is no explicit statement of when to prefer this over 'geocode' or the WGS84/LV95 converters, and no mention of prerequisites such as coordinates needing to be inside Switzerland.

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