Skip to main content
Glama

Send a fax

send_fax
Destructive

Use this to send a fax from the person's Faxette credit, or an organization's fax on its plan or card. For an organization's fax, pass the payment_method from get_fax's payment_option once the person agrees to it, and for saved_card its quote; amount_cents isn't needed. Only for a fax in their account that's ready to pay for: call get_fax first. Show the prepared PDF with open_fax_review or its review_url. Have the person confirm the destination, documents and credit_price, explain that it comes from their credit, and call this only once they clearly agree. If get_account shows their credit doesn't cover it, give them the status page instead, where they can pay for this fax by card. For the EU connector, also explain that sending starts immediately and the person's right to cancel ends once the fax is delivered. Obtain their explicit agreement before setting immediate_sending_consent to true. Needs the person to sign in to Faxette; calling it while they aren't asks the app to sign them in.

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": {
      "id": "<id>"
    },
    "name": "send_fax"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe fax's id, from create_fax, get_faxes or get_fax.
quoteNoThe credit_quote returned by get_fax for the exact destination, PDF and price the person reviewed and approved. After quote_changed or quote_required, show the new proof and obtain fresh approval.
amount_centsNoThe credit_price amount_cents from get_fax that the person agreed to. If the fax's documents changed since, Faxette refuses with price_changed: call get_fax and confirm the new price.
payment_methodNoOnly for an organization's fax: the payment_option's payment_method the person agreed to. If it changed, Faxette refuses with payment_changed: call get_fax and confirm again.
immediate_sending_consentNoRequired as true for EU credit sends, only after the person explicitly agrees to immediate sending and acknowledges that their right to cancel ends on delivery. Never infer this from agreement to the price alone.

Output Schema

NameRequiredDescriptionDefault
idYesThe fax's id. Pass it to get_fax when the person is signed in.
priceYesBefore tax. Null until the pages are counted.
statusYesdraft: 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.
attemptYesThe current attempt to dial the fax number.
paymentYesThe person's payment once they start paying, by card or from their credit. amount_cents includes tax.
languageNo
resend_byYesFor a failed fax: until when the person can correct the fax number on the status page and send it again.
fax_numberYes
page_countYesNull until the pages are counted.
review_urlNoA private review link, valid for 30 minutes. Give it to the person so they can inspect the prepared PDF before paying.
status_urlYesThe page where the person checks the fax and pays. Give it to them.
max_attemptsYes
checkout_quoteNo
failure_reasonYesFor a failed fax: temporary (busy or no answer on every attempt), wrong_number (no fax machine answered), or our_side.
document_errorsYesFiles Faxette couldn't use. position is the file's number in the fax. The person fixes them on the status page.
next_attempt_atYesWhen the next attempt dials, if the line was busy or didn't answer.
checkout_availableYesTrue when the person can pay on the status page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payment_method
      Added value: +{
      +  "description": "Only for an organization's fax: the payment_option's payment_method the person agreed to. If it changed, Faxette refuses with payment_changed: call get_fax and confirm again.",
      +  "enum": [
      +    "plan",
      +    "saved_card"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "quote",
      -  "id",
      -  "amount_cents"
      -]New value: +[
      +  "id"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / quote
      Added value: +{
      +  "description": "The credit_quote returned by get_fax for the exact destination, PDF and price the person reviewed and approved. After quote_changed or quote_required, show the new proof and obtain fresh approval.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "amount_cents"
      -]New value: +[
      +  "quote",
      +  "id",
      +  "amount_cents"
      +]
    • addedOutput schema / properties / checkout_quote
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / language
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / review_url
      Added value: +{
      +  "description": "A private review link, valid for 30 minutes. Give it to the person so they can inspect the prepared PDF before paying.",
      +  "format": "uri",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / immediate_sending_consent
      Added value: +{
      +  "description": "Required as true for EU credit sends, only after the person explicitly agrees to immediate sending and acknowledges that their right to cancel ends on delivery. Never infer this from agreement to the price alone.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag a destructive, non-idempotent, open-world write, but the description adds substance beyond them: charges come from the person's credit or an organization's plan/card, sending starts immediately, the EU right to cancel ends on delivery, explicit consent must be obtained before setting immediate_sending_consent, and the call triggers an app sign-in prompt if the user is not authenticated. These are consequences an agent cannot infer from the annotations alone.

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?

Purpose is front-loaded and the rest is sequenced as prerequisites, confirmation steps, fallback, and EU consent, so each block corresponds to a decision the agent must make. It is dense and fairly long, with some conditional branching that could be tightened, but no sentence is purely filler.

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?

For a five-parameter, destructive, paid operation with an output schema, the definition covers authentication, required sequencing with get_fax/open_fax_review/get_account, consent and legal obligations, and where the refusal paths (price_changed, quote_changed, payment_changed) lead. Return values are left to the output schema, which is the correct division of labor.

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 per-field documentation is already carried by the schema and a 3 baseline would apply. The description still adds cross-tool semantics the schema does not: payment_method must be taken from get_fax's payment_option, saved_card uses the quote instead, and amount_cents is not needed in that path — clarifying which combination of optional fields is valid per payment route.

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 ('send a fax') and immediately scopes it by payment source (personal Faxette credit vs. an organization's plan or card). It also fences off the operation from the creation step by saying it is 'only for a fax in their account that's ready to pay for: call get_fax first', so an agent can distinguish it from create_fax, get_fax and resend_fax 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 Guidelines5/5

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

Explicit preconditions and alternatives are given: call get_fax first, show the PDF via open_fax_review or review_url, obtain confirmation of destination/documents/credit_price, and only invoke when the user clearly agrees. It also handles the negative branch — if get_account shows insufficient credit, direct the user to the status page instead — which is exactly the when-not-to-use guidance most descriptions omit.

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.