Skip to main content
Glama

Geocode a Swiss address or place

geocode
Read-only

Converts Swiss addresses, place names, and postal codes into WGS84 and LV95 coordinates. Search street addresses, municipalities, or PLZ codes to get precise geodata for mapping and verification.

Instructions

Search Swiss addresses, places, municipalities and postal codes and return coordinates (WGS84 + LV95). Works with street addresses ('Bundesplatz 3 Bern'), place names ('Matterhorn'), and PLZ codes.

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": {
      "query": "<query>"
    },
    "name": "geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesAddress, place name or postal code to search
originsNoComma-separated source filter: address, zipcode, gg25 (municipalities), district, kantone, gazetteer. Default: all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value beyond them by stating the geographic scope (Switzerland only) and the return payload (WGS84 + LV95 coordinates, two systems at once), which is the key behavioral fact an agent needs before calling.

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 sentences with the return value front-loaded and the input forms immediately after; nothing is padded. The example list is slightly redundant with the schema's own query description, which keeps it from a 5.

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?

With no output schema, the description carries the burden of explaining returns and does state both coordinate systems. It stops short of describing the result record shape (labels, IDs, confidence, ordering), which for a multi-result geocoder would be genuinely useful, but nothing needed to call it correctly is missing.

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%, so all three parameters (query, limit, origins) are already documented, including the origins source list. The description only restates the accepted query forms in example form and adds nothing about limit behavior or how origins interacts with result types, so the 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 gives a specific verb and resource set: it searches Swiss addresses, places, municipalities and postal codes and returns coordinates. The concrete examples ('Bundesplatz 3 Bern', 'Matterhorn', PLZ codes) make the forward-geocoding intent unmistakable versus the sibling reverse_geocode, though the sibling is never named explicitly.

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 implied by the input examples (address in, coordinates out), which is enough to select this over reverse_geocode by name alone. There is no explicit 'use this when…' framing, no mention of when NOT to use it, and no routing to siblings such as reverse_geocode or convert_wgs84_to_lv95.

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