Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_phone_e164_formatter

Format phone numbers to E.164 with country detection and validity checks, producing standardized output for records, documents, and integrations.

Instructions

[Document Utilities] Format a phone number to E.164 with country detection and validity check 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": {
      "phone": "<phone>"
    },
    "name": "caelara_docs_phone_e164_formatter"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesPhone number
countryNoDefault ISO-2 country code, e.g. US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 and does add value: it discloses measured latency (p50 10 ms, p95 14 ms) and that a validity check is performed, implying invalid numbers are detected. It never states what happens on an invalid number (error vs. flagged result) or what exactly is returned, which matters for a validation-bearing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and tight, but the '[Document Utilities]' prefix, the benchmark citation, and the documentation URL are boilerplate that does not help an agent decide or invoke the tool. Roughly a third of the text does not earn its place.

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 simple two-parameter utility with fully described schema this is mostly adequate, but with no output schema the description should say whether the result is an E.164 string plus validity flag, and how failures surface. Latency and provenance are covered; return semantics are 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 coverage is 100%, so both parameters are already documented. The phrase 'country detection' adds a useful nuance, that country is a default rather than a hard requirement, but no syntax or format details beyond the schema's own examples are supplied.

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 states a specific verb and resource ('Format a phone number to E.164') and adds two concrete behaviors: country detection and a validity check. It does not distinguish itself from related normalization siblings such as the address normalizer, but the resource is unambiguous.

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 explicit when-to-use guidance, no prerequisites, and no exclusion of alternatives; the agent must infer that this is the tool for phone numbers rather than, say, addresses. The behavior of requiring a country only as a fallback is only loosely implied by 'country detection'.

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