Skip to main content
Glama
bitterdev

pixelletter-mcp

Send fax

send_fax

Send documents or plain text as a fax. Specify the fax number, attach files or write text, and enable test mode to avoid real charges.

Instructions

Sends documents or plain text as a fax through PixelLetter, without posting a letter. Additional services such as registered mail do not apply to faxes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoLetter text as plain text, no HTML. Long texts run onto more pages automatically, your sender address is added by PixelLetter. "%Unterschrift%" on its own line inserts the signature stored in your PixelLetter account.
filesNoAbsolute paths of the documents to send, for example the PDF written by pdf-letter-mcp. Several files are converted and merged into one letter, in this order. Allowed: .pdf, .doc, .xls, .ppt, .rtf, .wpd, .psd, and PDF is the only type that always works.
addressNoRecipient address, one line per array entry, country included. PixelLetter typesets it. Required when no file is sent.
controlNoRaw value for the control field of the interface. The only value in public use is NODUPLEX, which the duplex parameter sets for you, so only reach for this when PixelLetter gave you another token.
subjectNoSubject of the letter.
locationNoDispatch centre: 1 = Munich (DE), 2 = Hausleiten near Vienna (AT), 3 = Hamburg (DE). Default of the API is 1.
testModeYesTest mode. true runs the order exactly like a real one but PixelLetter never prints, never sends and never charges. false really sends the letter. Always required, so nothing goes out by accident.
faxNumberYesFax number in international format, for example "+49 89 72448483".
inlineFilesNoDocuments passed as base64 instead of a path.
transactionNoYour own transaction id or short note. PixelLetter returns it with the response.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as authentication needs, rate limits, or what happens upon success or failure. The testMode parameter indicates a test mode, but the description does not elaborate on its behavior beyond the schema.

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?

The description is two sentences, front-loading the core purpose and adding a clarifying detail about additional services. No wasted words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 10 parameters and no output schema, the description remains minimal. It does not explain operational behavior, return values, or error cases. The schema covers parameters, but the description lacks completeness for effective agent usage without additional context.

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 existing parameter descriptions are detailed (e.g., for text, files, address). The tool description adds no new parameter-level information beyond what the schema provides, meeting the baseline expectation.

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 description clearly states it sends documents or plain text as a fax via PixelLetter, specifically noting it does not post a letter. This differentiates it from the sibling tool 'send_letter' and clarifies that additional services like registered mail do not apply.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for faxing rather than mailing, but does not provide explicit when-to-use or when-not-to-use guidance. The mention that registered mail does not apply offers some direction, but alternatives like 'send_letter' are not mentioned in the description itself.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitterdev/pixelletter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server