Skip to main content
Glama

Prepare a fax (returns a link to confirm and pay)

send_fax

Prepares a fax of a PDF to a fax number and returns a confirmation link. The fax is NOT sent and nothing is charged until the person opens the link, checks the pages and number, pays or uses their FaxUp credits, and presses Send on faxup.net. The PDF comes as file_url (a public https link) or file_base64. The result includes confirm_url, the link the person opens.

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": "send_fax"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoA file the person attached in ChatGPT (filled in by the host).
coverNoOptional cover page, added ahead of the document on faxup.net.
countryNoISO country code for a number given without "+", e.g. "GB".
file_urlNoPublic https:// link to the PDF.
filenameNoName shown to the person, e.g. "lease.pdf".
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`.
file_base64NoThe PDF itself, base64-encoded (up to 25 MB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds genuinely useful behavior beyond them: no fax is transmitted and nothing is charged until the recipient confirms and pays on faxup.net. However, it doesn't say what happens to a stale confirmation link, whether repeated calls create duplicate pending faxes (relevant since idempotentHint=false), or any rate/cost limits for the prepared fax itself. Good added context, but not complete.

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?

Three sentences, front-loaded with the action and the key safety caveat (not sent, not charged) before the input/output detail. The final sentence about confirm_url slightly restates the link already introduced in sentence two, but is justified because no output schema exists.

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 7-parameter, nested-object, no-output-schema tool, the description is strong: it covers the send/no-charge model and the two file input paths. The optional cover, filename, and country parameters are left entirely to the schema, which documents them fully, so an agent can still call correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3. The description still adds value the schema does not: it frames file_url and file_base64 as interchangeable ways to supply the same PDF ("or"), clarifying they are alternatives rather than complements, and it names confirm_url as the meaningful result field in the absence of an output schema. It says nothing about cover, filename, or country, which the schema already covers.

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 concrete verb and resource ("Prepares a fax of a PDF to a fax number") plus the immediate outcome ("returns a confirmation link"). The sibling tools are all lookup/utility tools (get_fax_status, format_fax_number, get_price_quote), so an agent can tell this is the only action-initiating tool without opening any schema.

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?

Explains the context of use clearly: this is a two-step flow where the fax is not sent until the person opens the link, verifies pages/number, pays or uses credits, and presses Send. It doesn't name an explicit alternative or when-not-to-use condition, but no sibling performs this action, so the gap is minor.

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