Skip to main content
Glama

search_postcode

Read-onlyIdempotent

Look up Swiss postal codes (PLZ) by city or locality name to convert a place name into its corresponding postcodes.

Instructions

Postcodes (PLZ) for a city/locality name

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

Input Schema

NameRequiredDescriptionDefault
city_nameYese.g. Zürich

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / city_name / description
      Previous value: -"City or locality name, e.g. \"Zürich\", \"Bern\", \"Locarno\""New value: +"e.g. Zürich"
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond that: it does not say whether city-name matching is exact or fuzzy, whether partial names or alternate spellings work, or whether multiple localities return multiple postcodes. For an openWorld lookup tool, that matching behavior is the main thing an agent needs to know.

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 definition is a single short, front-loaded phrase with no filler or redundancy. Its brevity is efficient, though it slides toward under-specification rather than true concision.

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?

With one required parameter, rich annotations, and no output schema, the definition is barely adequate: 'Postcodes (PLZ)' hints that a list of postcodes comes back, but return shape and match tolerance are undocumented. Minimum viable for a simple lookup, but with clear gaps an agent would hit on first call.

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% and the single parameter already carries an example ('Zürich'), so the schema does the heavy lifting. The description's wording 'city/locality name' slightly broadens the semantic field to include locality-level names, but adds no formatting, language, or matching rules beyond the schema.

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 phrase 'Postcodes (PLZ) for a city/locality name' identifies the resource (postcodes) and the input dimension (city/locality name), but it is a noun fragment with no explicit verb, leaving it ambiguous whether it is a search or a lookup. It also does not differentiate from the nearby siblings lookup_postcode and list_postcodes_in_canton, so an agent must infer the direction of the mapping.

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, no stated preconditions, and no mention of the alternatives among the siblings (lookup_postcode for the reverse direction, list_postcodes_in_canton for administrative listing). The agent is left to infer selection from the name alone.

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