Skip to main content
Glama

Send a Fax

send_fax
DestructiveIdempotent

Transmit an APPROVED fax via Phaxio. Refuses drafts that were never approved and faxes that were already sent — a fax can be transmitted exactly once.

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": {
      "api_key": "<api_key>",
      "fax_id": "<fax_id>"
    },
    "name": "send_fax"
  }
}

Input Schema

NameRequiredDescriptionDefault
fax_idYesthe fax_id returned by create_fax_draft.
api_keyYesyour 3L-Group Technology API key (lms_...).

Output Schema

NameRequiredDescriptionDefault

No arguments

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 flag the call as non-read-only, destructive, and idempotent; the description adds the valuable behavioral facts that it is an external transmit via Phaxio and that invalid-state calls are refused rather than silently succeeding. The exactly-once statement is consistent with idempotentHint=true rather than contradicting it. Missing only things like cost, rate limits, or failure modes mid-transmit.

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?

Two short sentences with zero filler; the prerequisite state is front-loaded and the refusal semantics follow immediately. Nothing repetitive or padded.

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 mutation with an output schema and full annotations, the description covers purpose, prerequisite state, and refusal behavior adequately. It stops short of operational context such as cost, delivery timing, or what the returned status looks like, but the output schema absorbs the latter.

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 self-documented (fax_id from create_fax_draft, api_key), so the schema carries the load. The description adds no format or usage detail about either parameter beyond what is already structured.

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?

States a specific verb and resource (transmit a fax) and pins down the required state ('APPROVED'), which separates it from create_fax_draft and approve_fax without opening any schema. The provider name (Phaxio) adds a concrete execution detail.

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?

Gives explicit preconditions and exclusions: refuses un-approved drafts and refuses faxes already sent, so the agent knows when not to call. It does not name sibling tools outright (e.g., 'use approve_fax first'), leaving the routing to inference from the state requirements.

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.