Skip to main content
Glama
klodr

faxdrop-mcp

faxdrop_send_fax

Destructive

Send a real fax to a fax number using a document from the outbox. Supports PDF, DOCX, JPEG, and PNG files with an optional cover page.

Instructions

Send a real fax via FaxDrop.

USE WHEN: user needs to fax a document (PDF, DOCX, JPEG, PNG ≤10MB) to a fax number — medical records, legal forms, government submissions, recipients who only accept fax.

DO NOT USE: for digital delivery (email, sftp), for files outside the outbox, for non-fax numbers — the 3-layer phone gate (TYPE → COUNTRY → per-number policy) rejects mobile/landline/premium.

SIDE EFFECTS: charges FaxDrop balance (or consumes free credits + adds branded cover on free tier), creates an audit log entry, allocates a fax ID server-side. ALWAYS confirm recipient + file + cover with the user before calling.

FILE LOCATION: document must live inside the outbox (default ~/FaxOutbox/, override via FAXDROP_MCP_WORK_DIR). Files outside are rejected — ask the user to copy in first.

RETURNS: { faxId, status: "queued", ... } — poll with faxdrop_get_fax_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the document to fax (PDF, DOCX, JPEG, or PNG, ≤10MB).
recipientNumberYesRecipient fax number, international (E.164) format with leading + and country code, e.g. +12125551234
senderNameYesSender display name shown on the cover page.
senderEmailYesSender email for delivery confirmation.
includeCoverNoInclude a FaxDrop cover page. Free accounts always include a branded cover regardless; paid accounts default to false. The cover-page fields below (coverNote, recipientName, subject, senderCompany, senderPhone) are only printed when includeCover is true.
coverNoteNoMessage printed on the cover page (max 500 chars). Only used when includeCover is true.
recipientNameNoRecipient display name on the cover page, e.g. "Dr. Jane Smith" (max 50 chars).
subjectNoCover page subject / RE: line (max 200 chars).
senderCompanyNoSender company shown on the cover page (max 100 chars).
senderPhoneNoSender callback number shown on the cover page (E.164 format).
Behavior5/5

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

The description adds significant behavioral context beyond annotations: charges to balance, free tier adds branded cover, creates audit log, allocates fax ID, and requires file in outbox. Annotations (destructiveHint, openWorldHint) are consistent and enhanced.

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

Conciseness4/5

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

The description is well-structured with headings (USE WHEN, DO NOT USE, etc.) and front-loaded. However, it is slightly verbose—some information about file location appears twice—but remains clear and organized.

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?

The description covers all necessary aspects: purpose, usage rules, side effects, file constraints, and return format (faxId, status) with a recommendation to poll. Given the complexity (10 params, no output schema), it is thorough and self-contained.

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?

With 100% schema coverage, the description still adds value by explaining the outbox requirement, cover page behavior (free vs paid), and conditions for cover fields. This clarifies nuances beyond the schema descriptions.

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 explicitly states 'Send a real fax via FaxDrop', lists supported file types and size limit, and distinguishes from sibling tools (faxdrop_get_fax_status, faxdrop_pair_number). It also specifies when to use (e.g., medical records) and when not to use (digital delivery, non-fax numbers).

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

Usage Guidelines5/5

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

It provides explicit 'USE WHEN' and 'DO NOT USE' sections, detailing allowed document types, file size, and recipient restrictions. It also gives instructions on file location in the outbox and advises to confirm with the user before calling.

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/klodr/faxdrop-mcp'

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