Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_address_normalizer

Normalize free-form postal addresses by standardizing casing, street/directional abbreviations, units, ZIP codes, and state fields for consistent records.

Instructions

[Document Utilities] Normalize a postal address: casing, street/directional abbreviations, unit, ZIP and state Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.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": {
      "address": "<address>"
    },
    "name": "caelara_docs_address_normalizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFree-form address

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 behavior burden, and it does add real value: it lists the normalization dimensions, gives measured p50/p95 latency, and points to docs. However, it omits error handling for unparseable or non-US addresses (the mention of ZIP/state implies a US-centric assumption), whether the operation is deterministic/idempotent, and whether the 'state' normalization means abbreviation or expansion.

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?

Front-loaded with the bracket tag, then the one substantive sentence stating exactly what is normalized, then operational metadata. The benchmark and docs URL are mildly noisy but genuinely useful for routing decisions; no sentence is wasted.

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-string-in tool with no output schema, the description should state the return shape (a single normalized string versus split components), since the mention of unit, ZIP and state suggests parsing. That gap, plus absent error behavior, leaves it adequate but incomplete.

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?

There is a single parameter with 100% schema description coverage ("Free-form address"), so the schema baseline applies. The description adds a little context by implying what the input form looks like, but it adds no language, format, or length constraints beyond the schema.

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?

Names a specific verb ("Normalize") and resource ("postal address") and enumerates exactly what is normalized: casing, street/directional abbreviations, unit, ZIP and state. It does not name or contrast any sibling (e.g., the phone E.164 formatter), so an agent must infer the boundary from the resource noun alone.

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 only implied: an agent can deduce it should call this when it has a messy free-form address, but there is no explicit when-to-use, no precondition (e.g., must be a single postal address rather than a fragment), and no statement about when not to use it.

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