Skip to main content
Glama

IRLsend Postcards

Design a postcard

design_postcard

Design a real printed postcard that IRLsend mails to someone in the US. Use it when the user wants to thank a client, customer or employee, follow up with a sales lead or prospect so they remember them, send a birthday, holiday, sympathy, get-well or just-because card, or reach someone by real mail instead of email or text. Makes a 6x9 inch card (front picture, back message) for free and returns a preview and a link where the sender adds one mailing address or a whole list (a holiday list, every client; each card gets its person's first name) and pays $5 a card (printing and First-Class postage included). Do not include any street address, phone number or email.

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": {
      "occasion": "<occasion>",
      "recipient_first_name": "<recipient_first_name>",
      "message_or_idea": "<message_or_idea>",
      "sign_off": "<sign_off>"
    },
    "name": "design_postcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
occasionYesThe occasion, e.g. birthday, thank you, client thank-you, sales follow-up, holiday, sympathy, work anniversary, get well, just because.
sign_offYesHow the card is signed, e.g. "Love, Sam".
style_hintNoOptional look, e.g. sunflowers, watercolor beach, bold words, playful, formal.
card_formatNoOptional: the kind of card the sender named, e.g. postcard, folded card, letter, 4x6. IRLsend mails 6x9 postcards; any other format is noted and the card is made as a 6x9 postcard.
message_or_ideaYesWhat the back should say. Put the sender's exact words in double quotes to print them as written; otherwise give the idea and details and the message is written for them.
recipient_first_nameYesThe recipient's first name, as it should appear on the card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that design is free, the card is 6x9, the tool returns a preview plus a link, and that address entry and the $5/card charge (printing plus First-Class postage) happen at that link rather than inside this call — consistent with openWorldHint=false and destructiveHint=false. It omits what calling it twice does (idempotentHint=false implies duplicate designs), so it is strong but not exhaustive.

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?

A single dense paragraph that front-loads purpose, then use cases, then mechanics and cost. Slight redundancy between the long occasion list and the earlier 'thank a client, customer or employee' phrasing, but no sentence is wasted.

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?

With no output schema, the description carries the return burden and does so by describing the preview and the address/payment link. Pricing, format and per-recipient personalization are all covered; only repeat-invocation and revision behavior are left implicit for an agent to infer.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns more by explaining that a list of addresses at the link personalizes each card with its recipient's first name, and by constraining message content away from street addresses, phone numbers and emails. It still leaves style_hint, card_format and sign_off to the schema.

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 ('Design a real printed postcard that IRLsend mails') and immediately pins down the output artifact (6x9 card with front picture and back message). It is clearly distinguishable from revise_postcard and check_postcard_order, which act on an existing order rather than creating a new design.

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 a rich set of triggering situations (client thank-you, sales follow-up, birthday, holiday, sympathy, get-well, just-because, or reaching someone by mail instead of email/text) plus an exclusion ('Do not include any street address, phone number or email'). It does not explicitly route to revise_postcard or check_postcard_order, so it stops short of the top score.

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