Skip to main content
Glama

Caelara Labs Document Utilities

phone_e164_formatter

Format a phone number to E.164 with country detection and validity check

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

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two real behaviors beyond the name: automatic country detection and a validity check. It does not say what happens on an invalid or unparseable number (throw vs. return a flag vs. best-effort passthrough), and with no output schema the return shape stays ambiguous given the word 'check'.

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?

One front-loaded sentence with no filler; the transformation, the detection behavior, and the validation behavior are all packed in without redundancy.

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 low-complexity, fully-documented two-parameter transform this is nearly adequate, but with no annotations and no output schema the definition leaves open what a 'validity check' returns and how invalid input is surfaced - the one thing the description should have compensated for.

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%, including that country is an ISO-2 default, so the schema already does the heavy lifting. 'Country detection' in the description hints that the country param is a fallback for undetectable numbers, which is modest added meaning but not a format or precedence rule.

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?

States a specific verb (format) plus resource (phone number) plus the target standard (E.164), and adds two capability hints (country detection, validity check). No sibling in the list touches phone-number semantics, so explicit differentiation isn't needed, but the description doesn't say that 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 only implied by the resource type - an agent can infer 'use when you have a phone number needing E.164 normalization' - but there is no explicit when-to-use statement, no exclusions, and no mention of what to do if the number is already E.164.

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