Skip to main content
Glama

Find postal codes for a locality

search_locality
Read-only

Find Swiss localities by name in the official directory and return their postal codes, helping resolve place names to postal codes for Swiss addresses.

Instructions

Search Swiss localities by name in the official directory and return their postal code(s).

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

Input Schema

NameRequiredDescriptionDefault
nameYesLocality name, e.g. 'Winterthur'
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/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 that results come from the 'official directory' and that a locality may yield multiple postal codes ('postal code(s)'), but says nothing about how results are limited, ranked, or returned.

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?

A single front-loaded sentence with no filler, stating both the lookup and the return value.

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 simple read-only lookup with no output schema, the description correctly conveys the return value (postal codes). It omits result-count behavior, matching rules for ambiguous locality names, and any mention of the otherwise undocumented limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'name' is documented with an example, but 'limit' (default 10, max 50) has no description anywhere. The description reinforces that matching is by name but does not explain the result cap or what the limit controls, so it does not compensate for the coverage gap.

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?

States a specific verb and resource (search Swiss localities by name) and the output (postal codes) from an authoritative source. It is clearly distinct from the sibling set, which covers codes, companies, parliament, etc., though it does not explicitly name any alternative.

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: use when you have a locality name and need its postal code. There is no explicit when-not guidance, no mention of alternatives, and no note on what to do when the name is ambiguous or unmatched.

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