Skip to main content
Glama

reverse_geocode

Read-onlyIdempotent

Convert WGS84 latitude and longitude coordinates into a Swiss address using swisstopo data, so you can identify locations from raw GPS points.

Instructions

WGS84 coordinates to address (swisstopo)

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>",
      "lng": "<lng>"
    },
    "name": "reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lngYesLongitude (WGS84)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare the safety profile: read-only, idempotent, non-destructive, and openWorld, so the description adds little. The parenthetical 'swisstopo' conveys useful provenance, identifying the official Swiss federal data source, which affects expected accuracy and coverage, but the description says nothing about behavior outside Swiss borders, error responses, or the returned address structure.

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?

The description is a single five-word fragment with zero padding, and the key information appears immediately. However, it is telegraphic to the point of omitting a verb, so the wording prioritizes brevity over clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 whose annotations and schema are complete, this is close to sufficient. Still, the description never says what the output contains, such as whether it returns an address, a municipality, or coordinates matched to data coverage, and it does not note whether it covers only Switzerland; with no output schema, that gap matters somewhat.

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% for both parameters: lat and lng already carry the 'WGS84' unit label. The description merely restates the same coordinate-system fact and adds no new syntax, ordering, or range detail, 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?

The description states the transformation concisely: it converts WGS84 coordinates into an address, as a reverse lookup. The agent can determine what the tool does, but the telegraphic fragment lacks a clear verb. It also never distinguishes this tool from its sibling `geocode` (forward geocoding) or `identify_location`, so the separation depends on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no directives about when to choose this tool over the alternatives `geocode`, `identify_location`, or `search_places`, and it states neither prerequisites nor the reverse condition, such as routing forward lookups elsewhere. The only usage signal is the implied direction: coordinates to address.

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