Skip to main content
Glama

Prepare a fax

prepare_fax

Validate one PDF of up to 25 pages and create a fax draft with a 30-minute quote. Provide exactly one of upload_id or pdf_base64. This does not charge the account and does not send the fax.

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": {
      "destination_country": "<destination_country>",
      "recipient_name": "<recipient_name>",
      "recipient_fax": "<recipient_fax>",
      "sender_name": "<sender_name>",
      "sender_email": "<sender_email>",
      "sender_phone": "<sender_phone>",
      "filename": "<filename>"
    },
    "name": "prepare_fax"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesPDF filename.
upload_idNoSingle-use upload ID returned by create_pdf_upload after the PDF has been uploaded.
pdf_base64NoBase64-encoded PDF bytes. The PDF is delivered as-is; include a cover page in the document if one is needed.
sender_nameYes
sender_emailYes
sender_phoneYesUS or Canadian telephone number.
recipient_faxYesUS or Canadian fax number.
recipient_nameYes
sender_companyNo
client_referenceNo
recipient_companyNo
destination_countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, closed-world, so the safety bar is partly covered. The description adds real context beyond them: a 25-page validation cap, a 30-minute quote window, and the explicit assurance that neither account charging nor transmission occurs at this step.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and constraints, then the input-mode rule, then the negative side effects. Every clause carries information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tell the agent what comes back — it doesn't say whether a draft ID, quote ID, or expiry timestamp is returned, which matters for chaining into send_fax within the 30-minute quote. Coverage of the unlabeled schema parameters is also left thin, so the definition is adequate but has a clear gap at the hand-off point.

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?

With only 42% schema description coverage across 12 parameters, the description must compensate, and it does the most valuable part: the mutually exclusive 'exactly one of upload_id or pdf_base64' rule that the schema itself cannot express as an enum or oneOf. It adds nothing, however, about the required sender/recipient or destination_country fields.

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 specific verb and resource with hard constraints ('Validate one PDF of up to 25 pages and create a fax draft with a 30-minute quote'), then immediately scopes it against the neighbouring action ('does not send the fax'). An agent can distinguish this from send_fax without opening either 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?

Gives explicit routing guidance between the two input modes ('Provide exactly one of upload_id or pdf_base64'), which is the main fork an agent faces. It also sets expectations about side effects (no charge), but never explicitly says to call send_fax afterwards or when this tool is the wrong choice versus list_faxes/get_fax_status.

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