Skip to main content
Glama

Create a fax

create_fax

Prepare a fax for a person to send with PayPerFax, the pay-per-fax service: no account, no subscription, one payment for one fax. A common use is a letter or a form for the IRS, a doctor, a court, an insurer or a landlord.

The tool does not send the fax and does not charge. It returns a link for the person. The person opens the link, sees the preview and the price, and pays in the browser. Then the fax is sent.

Rules:

  1. Email: ask the person for their email address. Do not guess it. The confirmation and the receipt go there.

  2. A document that the person has as a file (a PDF, a scan, a signed form): do not retype it as text. A typed copy of a signed form is not the form. Set file_expected to true, and tell the person that they add the file on the page of the link.

  3. The fax number of an agency or a company: take it from its official website (for the IRS: irs.gov), and show the person the source. A number from memory can send private papers to a stranger.

  4. A letter that you write goes in markdown. With no cover page, the letter must have its own date, names and address block. With a cover page, keep cover_message short: a long message is cut off.

  5. Limits: the markdown text can be at most 100 KB. Headings, lists, bold text and tables are printed. An image is printed as its alt text, a link as its text, and raw HTML as text.

  6. If you can run shell commands and the document is a local file, send it with the HTTP call: curl -F "to=+14155550101" -F "email=person@example.com" -F "documents[]=@/path/to/file.pdf" https://fax.payperfax.com/api/fax

  7. After the call, give the person the link, and say that nothing is sent and nothing is charged before they pay. The confirmation email comes after the payment. If the status of the fax is later "failed", the person is not charged, and can send the fax again.

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": "<to>"
    },
    "name": "create_fax"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe fax number in international format: "+", the country code, the number. Example: +14155550101.
emailNoThe person's email address, for the confirmation and the receipt. Ask the person; do not guess. Required when you send markdown or a cover page.
countryNoThe person's country as a two-letter code (ISO 3166-1 alpha-2), for example US, DE, GB or JP. It sets the currency of the price, and the date format on the cover page and in the emails. Without it, the price is in US dollars, and the dates have the US format.
languageNoThe language of the pages that the person sees, and of the emails. The default is en.
markdownNoThe document as Markdown text that you wrote, for example a letter. Leave it out when the person has the document as a file.
timezoneNoThe person's time zone as an IANA name, for example America/New_York. Without it, times are shown in UTC.
cover_pageNotrue to put a cover page before the document. The default is no cover page.
sender_nameNoThe sender's name on the cover page. Only with cover_page. At most 100 characters.
cover_messageNoA short note on the cover page, as plain text, at most 5000 characters. Only with cover_page.
file_expectedNotrue when the person must still add a file (a PDF, a scan, a signed form). Then the link opens a form with what you sent, and the person adds the file there.
recipient_nameNoThe recipient's name on the cover page. Only with cover_page. At most 100 characters.
recipient_companyNoThe recipient's company or agency on the cover page. Only with cover_page. At most 100 characters.
show_sender_emailNotrue to show the person's email address on the cover page, so the recipient can reply. Only with cover_page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "de",
      -  "ja",
      -  "ko",
      -  "fr",
      -  "it"
      -]New value: +[
      +  "en",
      +  "es",
      +  "de",
      +  "ja",
      +  "ko",
      +  "fr",
      +  "it",
      +  "zh-tw"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / show_sender_email
      Added value: +{
      +  "description": "true to show the person's email address on the cover page, so the recipient can reply. Only with cover_page.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "de",
      -  "ja",
      -  "ko",
      -  "fr"
      -]New value: +[
      +  "en",
      +  "es",
      +  "de",
      +  "ja",
      +  "ko",
      +  "fr",
      +  "it"
      +]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive call; the description goes far beyond by disclosing the human-in-the-loop contract: nothing is sent and nothing is charged until the person pays in the browser, confirmation email arrives after payment, and a "failed" status means no charge with a retry possible. It also discloses the 100 KB markdown limit and how images, links, and raw HTML degrade to text — behavior unavailable anywhere else.

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?

Front-loaded: the first paragraph delivers purpose, the no-send/no-charge contract, and the return value before any rules. For a 13-parameter tool driving a multi-step flow the length is largely earned, but rule 7 restates the "nothing is sent and nothing is charged" promise already made in the intro, and the embedded curl recipe is reference material that could be trimmed.

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?

There is no output schema, so the description carries the full burden of explaining the return — it does so (a link the person opens to see preview and price), and covers the downstream lifecycle: payment, confirmation email timing, and failure handling. Currency and date-format consequences of country/language are also surfaced, leaving nothing an agent needs before calling.

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 is 3, but the description adds real meaning the schema lacks: the 100 KB markdown ceiling, the rule that a letter without a cover page needs its own date and address block, that cover_message is truncated when long, and that file_expected changes what the link opens into. Rule 1 also reinforces the email parameter's sourcing constraint (ask, never guess) with a stated reason.

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 opening sentence names a specific verb and resource ("Prepare a fax") plus the service it goes through, and immediately draws the boundary that matters most: the tool does not send and does not charge, it returns a link. That implicitly and cleanly separates it from the sibling get_fax_status, which covers what happens after.

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?

The seven numbered rules are explicit routing logic: use markdown when writing a letter, set file_expected when the person holds a file, never retype a signed form, source the fax number from an official website, and use the curl path when a local file and shell access exist. It states when-not conditions ("do not retype it as text") and alternatives (link flow vs. curl) rather than leaving them to inference.

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.