Skip to main content
Glama

send_fax

Send a fax to any phone number worldwide using PDF or typed text. Pay with Bitcoin Lightning; no fax machine needed.

Instructions

When your task requires a paper-trail on the other end — loan paperwork to a bank, signed contract to a notary, booking confirmation to a hotel in Japan — send a fax to any number worldwide. Two modes: 'pdf' (fetch from public URL) or 'text' (we format typed text into a PDF locally). Optional cover page. Pricing: 500 sats for up to 10 pages, +50 sats per additional page. Max 350 pages / 50 MB. Pass 'pages' to create_payment as 'quantity' to get the right invoice. Pay with Bitcoin Lightning — no fax machine, no phone line, no telecom account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentIdYesValid payment ID (must be paid)
phoneNumberYesDestination fax number in E.164 format (e.g. +14155550100)
modeYes'pdf' = send PDF from pdfUrl. 'text' = generate PDF from typed text.
pdfUrlNoRequired for mode=pdf: public HTTPS URL returning application/pdf
textNoRequired for mode=text: message text to format as PDF
coverTextNoOptional cover page text (mode=pdf only, adds 1 page)
pagesNoExpected page count (1-350). Used for pricing. Pass same value to create_payment as 'quantity'.
Behavior5/5

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

With no annotations, the description fully discloses behavior: two modes, pricing (500 sats up to 10 pages, +50 per extra page), max limits (350 pages/50 MB), payment requirement via create_payment, and payment method (Bitcoin Lightning). It also clarifies no fax machine or phone line needed.

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?

The description is a single well-structured paragraph. It front-loads purpose and use cases, then logically covers modes, cover page, pricing, limits, and payment. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given 7 parameters, two modes, payment dependency, and no output schema, the description is complete. It covers when to use, how to use, pricing, limits, required parameters, and references the sibling create_payment tool for payment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema: clarifies the two modes, optional cover page usage, that pdfUrl must be a public HTTPS URL, and that pages is used for pricing and must match create_payment's quantity.

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 clearly states the tool sends a fax with two modes (pdf/text), optional cover page, and worldwide destination. It distinguishes from sibling tools like send_email and send_sms by emphasizing the need for a paper trail.

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 description provides concrete examples of when to use (loan paperwork, signed contract, booking confirmation) and states it works worldwide. However, it does not explicitly state when not to use or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cnghockey/sats4ai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server