Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_geo_postal_code_validator

Validate and normalize postal codes for a specified country using ISO alpha-2 codes to confirm formatting and improve address data consistency.

Instructions

[Global Locale] Validate and normalize a postal code for a country Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://geo.caelaralabs.com.

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": {
      "country": "<country>",
      "code": "<code>"
    },
    "name": "caelara_geo_postal_code_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPostal code to validate
countryYesISO alpha-2 country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully signals that output may differ from input ('normalize'), and supplies measured latency (p50 12 ms, p95 14 ms) plus the upstream endpoint. However it never states what happens for an invalid code (error vs. a valid=false flag) or any shape of the result, which matters because there is no output schema.

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 core purpose is front-loaded in the first sentence, with only a short latency/endpoint tail. The benchmark timestamp and URL are boilerplate-adjacent but do convey operational expectations, so the text is reasonably tight.

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?

This is a simple two-parameter validator with no output schema and no annotations, so the description must cover both behavior and results. It covers the input side and performance, but an agent still cannot predict whether a failed validation yields an error or a structured response, which is the one thing left 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 both parameters (code, country) are already documented in the schema, giving a baseline of 3. The description adds only the notion that codes are country-scoped and globally supported; it contributes no format hints beyond the schema's 'ISO alpha-2' note.

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 pair (validate and normalize) and a precise resource (a postal code for a given country), plus a [Global Locale] scope tag. It clearly distinguishes the tool from geo siblings such as country_iso_enricher or business_hours_calc, though it doesn't name an alternative itself.

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 verb – validate a postal code when you need to check or canonicalize one – but there is no explicit when-to-use statement, no exclusions, and no guidance on when a sibling like country_iso_enricher would be the better call. Adequate but leaves the agent to infer.

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