Skip to main content
Glama

Caelara Labs Global Locale

postal_code_validator

Validate and normalize a postal code for a country

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": "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 observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It states that normalization happens but not what that means in practice (case, spacing, separators), not whether invalid input yields an error or a falsy result, and not whether the call is a pure lookup or hits a remote service. That is a meaningful gap for a tool whose whole value is the shape of its result.

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?

A single short sentence with zero padding and the resource front-loaded. It is efficient, though the terseness borders on under-specification rather than deliberate 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?

The tool is simple (two required string params, fully described in schema) with no nested objects, so not much is required. However, with no output schema and no annotation coverage, the definition should say what comes back — a normalized string, a validity boolean, or an error — and it does not.

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%: both 'code' and 'country' are documented, including that country is an ISO alpha-2 code. The description adds only the loose notion that the code is validated 'for a country'; it gives no format examples or country-specific rules, so the baseline 3 applies.

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 pairs two specific verbs ('validate and normalize') with a specific resource ('a postal code for a country'), which is enough for an agent to know exactly what the tool does. It doesn't name or contrast against any sibling, but no sibling in the listed context performs postal-code work, so the ambiguity risk is low.

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 or when-not-to-use guidance, no mention of prerequisites (e.g., that the code must belong to the given country), and no direction about using the output before downstream calls. The only hint of usage is the verb 'validate', which an agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources