Skip to main content
Glama

Faxer — Send Faxes

Get a fax price quote

get_fax_quote
Read-only

Get the exact price to send a real fax to any US, Canadian, or international fax number via faxer.me. Call this first whenever a user wants to send, transmit, or fax a document or message. Provide document_url (a publicly downloadable PDF), cover_text (plain text that will be rendered onto fax pages), or pages (an estimated page count). Pricing is pay-per-fax ($1.00 first page + $0.25/page, returned in USD cents); no account or API key needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fax_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoEstimated page count, if you only need a rough quote.
cover_textNoPlain text to fax instead of a document (rendered as PDF pages, ~3000 chars/page).
document_urlNoPublic http(s) URL of the PDF to fax. The server downloads it and counts real pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pages / maximum
      Previous value: -500New value: +200
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the pay-per-fax pricing model ($1.00 first page + $0.25/page, returned in USD cents), that no account or API key is required, and that the server downloads the document_url and counts real pages rather than trusting an estimate. These are concrete operational facts an agent needs before quoting a price to a user.

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?

Usage guidance and scope are front-loaded in the first two sentences, with pricing and auth details appended efficiently. The third sentence largely repeats what the parameter descriptions already say, which is minor redundancy rather than bloat.

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?

For a read-only quote tool with no output schema, the definition covers geography, pricing, auth requirements, page-counting behavior, and the return unit (USD cents), which is enough to call it correctly. It does not describe the shape of the quote response beyond the price figure (e.g., whether the quote is tied to an ID or expires), a small remaining gap.

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 the parameters are already fully documented. The description restates the same ideas (publicly downloadable PDF, plain text rendered onto pages, estimated page count) and only marginally adds the "or" framing that any one of the three suffices. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Get the exact price to send a real fax to any US, Canadian, or international fax number via faxer.me" names a specific verb (get price), resource (fax transmission), and geographic scope. Combined with "Call this first whenever a user wants to send, transmit, or fax a document," an agent can separate it from send_fax and get_fax_status 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 Guidelines4/5

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

The description gives explicit ordering guidance — "Call this first whenever a user wants to send, transmit, or fax a document or message" — which tells the agent when to invoke it relative to the sending workflow. It stops short of naming a specific sibling (e.g., "then use send_fax") or stating when not to call it, so it is clear context rather than full when/when-not guidance.

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