Skip to main content
Glama

Format a fax number for sending

format_fax_number
Read-onlyIdempotent

Turn a fax number into the international form FaxUp uses and check it can actually take a fax (right country, not a mobile or premium line). Read-only; sends nothing.

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": {
      "to_number": "<to_number>"
    },
    "name": "format_fax_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code for a number given without "+", e.g. "GB".
to_numberYesFax number in international form, e.g. "+1 202 555 0143" or "+44 20 7123 4567". Without a "+" it is read as US/Canada, or as `country`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only; sends nothing' adds little on its own. The description does add real behavioral content beyond the annotations by disclosing the validation rules — country eligibility and rejection of mobile or premium lines — which tells the agent the call can fail for reasons unrelated to syntax.

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 sentence, front-loaded with the primary action, with the safety disclaimer last. No filler wording; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only tool with full schema coverage and annotations, the description covers purpose, validation behavior and safety posture adequately. The one gap is that no output schema exists and the description never indicates what comes back — a normalized string, a validity flag, or an error on invalid input.

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% and both parameters are documented with examples and the country-code fallback rule in the schema itself. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (turn a fax number into the international form FaxUp uses) plus a second, clearly stated function (validate it can receive a fax). It implicitly separates itself from send_fax by noting nothing is sent, and from find_agency_fax_number by operating on a number the caller already has.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for sending' and 'sends nothing' establish the call as a formatting/validation step rather than a send operation, which gives clear context. It stops short of naming a specific alternative or explicitly saying 'call this before send_fax', so there is no explicit when-not guidance.

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