Faxette

Start a fax

create_fax

Use this once the person has confirmed the fax number, and given you their email if they aren't signed in. It creates the fax and returns status_url, the page where the person checks the fax number, documents and price, and pays to send it. Nothing is sent or charged until they pay there. Pass the document_ids from create_document. Without them, the fax waits on the status page for the person to add their files. Each call creates a separate fax. To see how a fax is doing, use get_fax_status, or get_fax when the person is signed in.

Input Schema

Name	Required	Description
`email`	No	The person's email address, where Faxette sends the receipt and updates. Ask the person for it. Leave it out when they're signed in: their account's email is used.
`fax_number`	Yes	The fax number the fax goes to, in international format, like +14155552671. Numbers in the US and Canada only.
`document_ids`	No	The document_id of each file from create_document, in the order they're faxed. Up to 10. Leave it out to let the person add files on the status page.

Output Schema

Name	Required	Description
`id`	Yes	The fax's id. Pass it to get_fax when the person is signed in.
`price`	Yes	Before tax. Null until the pages are counted.
`status`	Yes	draft: waiting for files, or for a file to be fixed. processing_documents: counting pages. documents_ready: ready to pay. awaiting_payment: the person is paying. scheduled: paid, about to dial. sending, delivered, failed. canceled: not paid in time.
`attempt`	Yes	The current attempt to dial the fax number.
`payment`	Yes	The person's payment once they start paying, by card or from their credit. amount_cents includes tax.
`resend_by`	Yes	For a failed fax: until when the person can correct the fax number on the status page and send it again.
`fax_number`	Yes
`page_count`	Yes	Null until the pages are counted.
`status_url`	Yes	The page where the person checks the fax and pays. Give it to them.
`max_attempts`	Yes
`failure_reason`	Yes	For a failed fax: temporary (busy or no answer on every attempt), wrong_number (no fax machine answered), or our_side.
`document_errors`	Yes	Files Faxette couldn't use. position is the file's number in the fax. The person fixes them on the status page.
`next_attempt_at`	Yes	When the next attempt dials, if the line was busy or didn't answer.
`checkout_available`	Yes	True when the person can pay on the status page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write, and the description adds genuinely new behavior: nothing is sent or charged until the person pays, and the fax waits on the status page for files when document_ids is omitted. Cost/side-effect disclosure of this kind is exactly what annotations can't convey, though "Each call creates a separate fax" largely restates idempotentHint=false.

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 precondition is front-loaded and every sentence carries operational weight — outcome, charge timing, document prerequisite, non-idempotency, next-step routing. It runs long for a three-parameter tool, but no sentence is filler.

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?

An output schema exists, so return values needn't be explained, yet the description helpfully names status_url as the person-facing page. Preconditions, charging behavior, and follow-up routing are all covered; the only omission is the create_fax versus send_fax boundary in a sibling set that exposes both.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents all three parameters, including the signed-in email shortcut and the omit-document_ids fallback. The description reinforces the same points (email only when not signed in, document_ids from create_document) but adds no new semantics such as ordering constraints beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("It creates the fax") and immediately describes the output artifact (status_url) and its role in the payment flow. It implicitly separates itself from send_fax via "Nothing is sent or charged until they pay there," but never names that sibling, so the differentiation is inferred rather than stated.

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?

Gives a concrete trigger condition ("once the person has confirmed the fax number, and given you their email if they aren't signed in") and explicitly redirects to get_fax_status / get_fax for follow-up. The notable gap is send_fax, a direct sibling that is never mentioned, so the agent must guess when to create versus send.

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

All Faxette tools Inspect

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.