Skip to main content
Glama

PayPerFax

by com.payperfax
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=false and destructiveHint=false; the description goes well beyond that. It discloses the full two-step flow (prepare → person pays in browser → fax sent), that nothing is sent or charged before payment, that confirmation arrives only after payment, and that a "failed" status means no charge and a possible retry. This is rich behavioral context an agent could not infer from the annotations.

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 opening paragraph is well front-loaded and the seven numbered rules are scannable and each carries distinct content. It is on the long side and some sentences read as workflow coaching rather than tool specification, but for a 12-parameter tool with a multi-step human-in-the-loop flow the length is largely earned.

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 must carry return-value disclosure, and it does: the tool returns a link for the person, and the fax outcome surfaces later via status. Combined with the payment/charge/failure semantics, an agent has everything needed to invoke the tool and set expectations for the person.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantics the schema lacks: the 100 KB markdown limit, that cover_message is truncated if long, that file_expected drives a form where the person uploads the file, and the email requirement for markdown/cover-page sends. It adds cross-parameter interaction guidance rather than restating field docs.

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 states a specific verb+resource ("Prepare a fax") and immediately scopes it: the tool does not send and does not charge, it returns a link. That framing cleanly separates it from the siblings get_fax_status (checking) and list_supported_formats (formats). An agent can tell what this tool does and does not do without opening the schema.

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?

Rules 1-6 give explicit when-to-use guidance: ask for email, do not retype a file the person already has (set file_expected), source the fax number from an official site, use markdown for letters you author. Rule 6 names a concrete alternative path (direct curl HTTP call for local files), which is exactly the alternative-routing the dimension rewards.

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

All PayPerFax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources