Skip to main content
Glama

Preview a letter with an enclosed image

quote_and_preview_letter_with_image

Preview a physical letter draft with an enclosed image after the signature. Requires a real U.S. recipient mailing address. Its answer says what sending it takes and when the mail usually arrives. If the user refers to an image already generated, shown, or attached earlier in this conversation, call this tool first to reuse that image. Otherwise prefer a direct file attachment or explicit imageUrl. Use upload_image only after an actual failed handoff or upload problem. A letter too long for one page runs on to a second or third page, printed on both sides and paid with Pay & Send; three pages is the longest. Only when the person asks for USPS Certified Mail (it costs more), pass mailService "certified"; "certified_return_receipt" adds an electronic return receipt. Certified mail is paid with Pay & Send, never a letter pack or a gift letter, and a new preview of a certified letter must pass mailService again. The person sends it on the page request_send links to: call request_send and give the person its link.

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": {
      "recipient": "<recipient>",
      "bodyText": "<bodyText>",
      "signOff": "<signOff>"
    },
    "name": "quote_and_preview_letter_with_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNo
senderNo
signOffYes
arriveByNoOptional. The date the mail should arrive by, YYYY-MM-DD, such as a birthday or an event. Letter IRL holds the mail and sends it to the printer in time; USPS does not guarantee First-Class dates. Omit it to mail as soon as possible.
bodyTextYes
headlineNoOptional, for the celebration stationery only: a short line printed large above the letter, such as "Happy Birthday, Sam!". It must fit on one line, and takes three of the page's lines; leave it out for confetti alone.
imageUrlNo
monogramNoOptional, for the monogram stationery only: the initials to print, one to three letters, such as "JMS". Leave it out to use the initials of the return address's name.
recipientYes
signatureNoOptional. Whether the letter prints the person's saved signature under the sign-off's first line (set_signature saves one). Left out, the person's last choice: on once a signature is saved. True with none saved is refused. Pass false to leave it off.
sendAsGiftNoSet true only when the user asks to send this as their gift letter: it is free and adds a printed page with a card for the recipient. Leave it out otherwise; a gift letter is then used only if the balance cannot pay.
stationeryNoOptional. The letter's stationery: classic, a plain page; monogram, initials in a ring; botanical, a line-drawn sprig; celebration, confetti with an optional headline; typewriter, the letter typed in a monospace face, which fits fewer words on the page; or handwritten, the letter in a handwriting face on faint ruled lines, which has no Greek, Hebrew or Vietnamese. Each but classic prints the date at the top right. Left out, the letter is in the account's last choice, or classic if it has none. Leave it out unless the user asks for a style or for a plain page (classic), or names an occasion a style suits.
mailServiceNoOptional. How the letter travels: standard (the default), certified (USPS Certified Mail, which gives a tracking number), or certified_return_receipt (Certified Mail with an electronic return receipt). Certified mail costs more and is paid with Pay & Send: no letter pack and no gift letter pays for it. Leave it out for an ordinary letter.

Output Schema

NameRequiredDescriptionDefault
pagesNoPresent only for a letter of more than one page: the pages it prints on, both sides of the paper. No letter pack or gift letter pays for it; it is paid with Pay & Send.
draftIdYes
giftCardNo
scheduleNo
signatureNoWhile signatures are offered: whether the letter prints the person's saved signature, and why
canSendNowYes
layoutTypeYes
stationeryNoWhile stationery is offered: the stationery the page was drawn in, with the date line, initials and headline it prints, and why: asked for, the account's last choice, or classic by default
mailServiceNoPresent only when the letter goes as certified mail: certified, or certified_return_receipt (with an electronic return receipt). Paid with Pay & Send.
wordsVersionNoWhile a letter's words can be changed in place: the version of the letter's words, which set_letter_words takes to say which words it replaces
arrivalWindowNoThe arrival dates that can be chosen now: what can be scheduled, not when this mail arrives
deliveryClassNo
contentVersionNoThe version of this mail as it is now: send it with the send, so what is mailed is what the person saw
draftExpiresAtYes
addressWarningsNo
lettersRequiredYes
sendEligibilityYes
deliveryEstimateNo
reasonCannotSendNo
deliveryDisclaimerNo
giftLettersAvailableNo
estimatedDeliveryDaysNo
savedReturnAddressNoteNo
usedSavedReturnAddressNo
senderAddressValidationNo
recipientAddressValidationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: requires a real U.S. recipient address, discloses page limits (three pages max, printed both sides), states that certified mail costs more, cannot be paid by letter pack or gift letter, and must be re-passed as mailService on a new preview. The response's content (cost and typical arrival) is also described.

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?

Front-loaded with purpose, then routing, then fulfillment behavior. Dense but nearly every sentence carries operational value; the closing request_send sentence is useful next-step guidance, though the certified-mail rules are spread across two separate sentences that could be consolidated.

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 13-parameter, open-world, non-idempotent preview tool with an output schema, the description covers the remaining gaps an agent would otherwise guess at: image sourcing priority, address requirement, page limits, paid-service constraints, and the handoff to request_send.

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?

With 54% schema coverage across 13 params, the schema already documents most optional fields in depth (stationery, mailService, arriveBy, signature, sendAsGift). The description adds the important behavioral rule that mailService must be repeated on a re-preview, but adds nothing about image/sender/recipient object fields or bodyText/signOff.

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 concrete verb and resource ('Preview a physical letter draft') plus the distinguishing trait ('with an enclosed image after the signature'), which cleanly separates it from quote_and_preview_letter and quote_and_preview_letter_with_header_image.

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 routing: call this first when the user refers to an image already generated/shown/attached; otherwise prefer a direct attachment or explicit imageUrl; use upload_image only after an actual failed handoff. It also scopes certified mail to an explicit user request and names the downstream sibling request_send for the actual send.

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