Skip to main content
Glama

lookup_postcode

Read-onlyIdempotent

Retrieve the locality, canton, and coordinates for a Swiss postcode (PLZ) to resolve location details from a 4-digit code.

Instructions

Locality, canton and coordinates for a postcode (PLZ)

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

Input Schema

NameRequiredDescriptionDefault
postcodeYes4 digits, e.g. 8001

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / postcode / description
      Previous value: -"Swiss postal code (PLZ), e.g. \"8001\" or \"3000\""New value: +"4 digits, e.g. 8001"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and repeatability are covered by structured data. The description contributes by stating the returned fields, which matters since no output schema exists, but says nothing about behavior for invalid or non-existent postcodes, coordinate format, or response shape.

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?

One short sentence, front-loaded with the output fields and the input identifier. Nothing is wasted, though the terseness leaves room for a clause that would cost nothing and disambiguate usage.

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 one-parameter read-only tool with full schema coverage and rich annotations, the description covers the essentials by naming return fields in the absence of an output schema. It stops short of specifying coordinate format, error behavior, or the relation to sibling search tools, which an agent still needs to call it with confidence.

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 coverage is 100%: the single 'postcode' parameter is documented as '4 digits, e.g. 8001'. The description only adds the German alias 'PLZ' and no extra syntax or constraint detail, so the schema does the heavy lifting and the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (postcode, with the PLZ alias) and enumerates the returned fields (locality, canton, coordinates), so the mapping is inferable. But it is a noun phrase with no verb and no differentiation from close siblings such as search_postcode, list_postcodes_in_canton, or geocode, leaving the agent to guess which lookup fits.

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?

There is no when-to-use guidance at all: nothing says whether this is for exact single-postcode resolution versus fuzzy search (search_postcode) or reverse geocoding. No exclusions or alternatives are named despite seven or more plausibly overlapping siblings.

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