Skip to main content
Glama

Caelara Labs Document Utilities

address_normalizer

Normalize a postal address: casing, street/directional abbreviations, unit, ZIP and state

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

Input Schema

NameRequiredDescriptionDefault
addressYesFree-form address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 behavioral burden, and it does disclose the concrete transformations performed (casing, abbreviations, unit, ZIP, state) — real value beyond the name. It says nothing about failure modes for unparseable or non-US addresses, ambiguity resolution, or whether the result is returned as a string or a structured object.

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 tight sentence with the verb and resource front-loaded and the normalized facets listed after the colon. Nothing is wasted and nothing is buried.

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, non-destructive utility this is close to sufficient: it says what it does and which fields it touches. However, with no annotations and no output schema, the description should have covered the return shape and behavior on invalid input, which it omits.

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?

Only one parameter exists and the schema already describes it fully as 'Free-form address' (100% coverage). The description adds the domain framing ('postal address') but no format hints, examples, or limits beyond what the schema states, 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 a specific verb ('Normalize') with a specific resource ('postal address') and enumerates the exact facets touched: casing, street/directional abbreviations, unit, ZIP and state. That makes the tool unmistakable against siblings like phone_e164_formatter or xml_to_json_clean, though it never explicitly contrasts itself with any of them.

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 prerequisites, and no mention of alternatives. A reader must infer that this is the tool for messy free-form address strings, and nothing warns about inputs it cannot handle.

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