Skip to main content
Glama

Check a preview

get_draft_status
Read-only

Used by Letter IRL's preview card: says whether a previewed letter or postcard is still ready to send, has been sent (with its order id and where that order stands), or has expired.

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": {
      "draftId": "<draftId>"
    },
    "name": "get_draft_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId from a letter or postcard preview

Output Schema

NameRequiredDescriptionDefault
sizeNoA ready postcard our renderer drew, while its sizes or layouts are offered: its size now. Its page goes to the card
pagesNoA ready letter of more than one page: the pages it is laid out on now
placeNoThe place the greeting names
layoutNoWith it, the postcard's front now
statusYes
captionNoThe border's caption, when it has one
draftIdYes
orderIdNoThe order the draft became, once sent
signOffNo
bodyTextNoA ready letter, while a letter's words can be changed in place (room to write, or the words editor): its words now, for the card
scheduleNoArrival dates, YYYY-MM-DD: a ready draft's, or a sent order's
signatureNoA ready letter our renderer drew, while signatures are offered: whether it prints the person's saved signature now; its page goes to the card
canSendNowNoA ready letter while room to write or certified mail is offered, or a postcard while its sizes or layouts are: whether the balance or a gift letter pays for it now
stationeryNoA ready letter's stationery now, while stationery is offered; its page goes to the card
cancellableNoA sent draft's order: whether it can still be cancelled free
mailServiceNoWith the terms, for a letter that is certified mail now, and for a sent letter that went by it: which service. Absent beside the delivery words: ordinary mail
orderStatusNoWhere a sent draft's order stands: scheduled while it waits for its mail date
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
deliveryClassNoWith the terms, for a letter that is certified mail or while certified mail is offered, and for a sent letter: how it is delivered, as a new preview would say it. A card draws it on its Delivery line
contentVersionNoThe version of this mail as it is now: send it with the send, so what is mailed is what the person saw
sendEligibilityNo
deliveryEstimateNoA ready draft's delivery estimate, with its dates now
reasonCannotSendNo
deliveryDisclaimerNoWith it, the words that qualify the delivery

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by disclosing the three possible outcomes and that a sent state carries an order id plus order standing, but it says nothing about expiry timing, error cases, or why idempotentHint is false for a pure lookup.

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?

One tightly packed sentence that front-loads the consumer ('preview card') and then enumerates the three states in a readable parenthetical. The opening clause is slightly incidental compared with the state enumeration, but nothing 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?

An output schema exists, so the description need not document the response shape; it nonetheless signals the state machine an agent must branch on. For a one-parameter read-only lookup this is close to complete, with only polling cadence and sibling boundaries left implicit.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that draftId comes from a letter or postcard preview. The description restates the same fact ('a previewed letter or postcard') without adding format, provenance, or reuse guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (a previewed letter/postcard draft) and the exact question it answers (ready to send / sent with order id and order standing / expired). It scopes itself to the preview card, which partly separates it from get_order_status and get_purchase_status, though it never explicitly contrasts with those siblings.

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?

Usage is only implied: 'Used by Letter IRL's preview card' suggests polling after a quote_and_preview_* call. There is no explicit when-to-use rule, no guidance on when to prefer get_order_status once an order exists, and no note on how often to re-check.

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