Skip to main content
Glama

Look up a Swiss postal code

lookup_postcode
Read-only

Resolve a 4-digit Swiss postal code (PLZ/NPA) to its locality or localities and coordinates for location-based lookups.

Instructions

Resolve a 4-digit Swiss postal code (PLZ/NPA) to its locality/localities with coordinates.

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": {
      "plz": "<plz>"
    },
    "name": "lookup_postcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYes4-digit Swiss postal code, e.g. '8001'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/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 still contributes real behavioral information by signalling that a single PLZ may resolve to multiple localities ('locality/localities'), which affects how the agent should handle results, but it says nothing about ambiguous or invalid codes or about coordinate reference system.

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?

One sentence, front-loaded with the verb and the input, with zero filler. Nothing can be trimmed without losing information, and the return shape and multiplicity caveat are packed into the same line.

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 one-parameter read-only lookup with no output schema, the description covers the input domain and sketches the return ('localities with coordinates'), which is largely sufficient. The main omission is the coordinate reference system (WGS84 vs LV95) — notable given siblings like convert_lv95_to_wgs84 — and there is no note on what happens for an unknown code.

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?

The single parameter has 100% schema description coverage, including the '^\d{4}$' pattern and an example, so the schema carries the parameter burden. The description only restates the 4-digit constraint and adds the PLZ/NPA naming aliases, which is marginal added meaning.

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 ('Resolve'), a specific resource ('4-digit Swiss postal code (PLZ/NPA)'), and even names the return content ('locality/localities with coordinates'). An agent can tell this apart from general-purpose siblings like geocode or get_swiss_municipality_facts, though no sibling is 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 only implied: if you hold a 4-digit Swiss PLZ and need its locality, this is the tool. There is no explicit when-to-use framing, no exclusions, and no pointer to alternatives such as geocode or lookup_code_list when the input is not a postal code.

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