Skip to main content
Glama

Draft a Fax

create_fax_draft

Create a fax DRAFT: validates the recipient number, counts the PDF's pages, screens its text, and returns a price quote (Phaxio per-page cost x pages + the flat $1.00 service fee). This NEVER transmits anything — call approve_fax, then send_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": {
      "api_key": "<api_key>",
      "to_number": "<to_number>",
      "pdf_path": "<pdf_path>"
    },
    "name": "create_fax_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesyour 3L-Group Technology API key (lms_...).
pdf_pathYespath to the PDF file on the server to fax.
to_numberYesrecipient fax number — 10-digit US number or a full E.164 number starting with +.
descriptionNooptional label for your own records.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the no-transmission guarantee and the exact cost formula (per-page rate x pages + $1.00 fee), which is real behavioral context an agent cannot get from readOnlyHint=false / destructiveHint=false. It does not address idempotency despite idempotentHint=false — whether re-running creates a duplicate draft or reuses one is left unstated.

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?

Two sentences, both earning their place, with the identity of the tool and its non-transmitting nature front-loaded before the workflow routing. No filler or restatement of the title.

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?

An output schema exists, so return-value documentation is unnecessary; the description still summarizes the return (a price quote) which is the key decision input. Combined with the required-parameter schema and the approve/send workflow, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so api_key, pdf_path, to_number, and description are already fully documented in the schema. The description mentions page counting and recipient validation, which loosely maps to pdf_path and to_number, but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 (create a fax DRAFT) and then enumerates the concrete work performed: number validation, page counting, text screening, and price quoting. The word DRAFT capitalized plus the explicit 'NEVER transmits' line separates it cleanly from send_fax and request_send.

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 sequencing guidance: 'call approve_fax, then send_fax', naming the exact siblings that follow this step. It also states the negative condition ('This NEVER transmits anything') so the agent knows this is the safe pre-flight step rather than the delivery step.

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.