Skip to main content
Glama

Certified Mail Sender

Send a paid letter now

send_letter_now
DestructiveIdempotent

Skip a paid letter's 30-minute cancellation hold when the person asks to send it right away. This never bypasses screening and does not submit immediately. Idempotent while paid, screening or held for review; refused before payment or after submission or cancellation. Cancellation stays possible until submission, with no guaranteed extra time. Read the returned cancel_until and next_step; only the hold is skipped. Use id with its creating API key, or the complete private letter_url. Example: {"letter_url":"https://certifiedmailsender.com/l/?t="}

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": "send_letter_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoLetter id; send the API key that created it in Authorization.
letter_urlNoComplete private letter_url or approval_url, including its t token.

Output Schema

NameRequiredDescriptionDefault
idYes
toYes
fromYes
modeYes
pagesYes
quoteYes
stateYesPersisted lifecycle state, not proof of mailing. printed comes from a Printed tracking observation; USPS acceptance requires proof_of_mailing. Reads can skip intermediate states. Test letters stop at submitted and never print or mail.
originYes
refundYesRefund record for a canceled, rejected or failed letter; null when no refund is due. Use state and amount_cents to tell the person what happened to their payment. Card refunds usually show within 5 to 10 business days; the bank decides exactly when.
serviceYes
send_nowYesWhether someone chose to skip the 30-minute cancellation hold. This never skips required payment or screening; auto-send keys have no per-letter approval step.
timelineYes
next_stepYes
created_atYesUTC RFC 3339 timestamp with milliseconds, YYYY-MM-DDTHH:mm:ss.sssZ.
letter_urlYesKeep this complete private link, including its t token. An anonymous letter can be read and canceled only with that token; an id alone or an API key created later cannot open it. A letter created with an API key can also be read and canceled with that same key.
preview_urlYes
receipt_urlNoPrivate token link to the USPS electronic Return Receipt PDF. Present only for certified_err in receipt_ready while files are retained; omitted means no downloadable receipt is available here, not that delivery failed. Keep the t token; this receipt is private like the letter PDF.
review_noteYes
address_noteYesThe address partner’s raw note, not wording to relay to the person. Use next_step for the plain-language version to tell the person.
approval_urlNoPrivate review page with the expected mailing date and USPS delivery estimate (not guaranteed). If the person mentioned a deadline, compare it with the delivery estimate and tell them plainly when the estimate falls after it.
cancel_untilYesThe scheduled end of the 30-minute cancellation hold, as an ISO 8601 / UTC RFC 3339 timestamp with milliseconds (YYYY-MM-DDTHH:mm:ss.sssZ); null for drafts or letters no longer cancellable. If skipped, this is when sending became eligible after payment. Cancellation remains possible until actual submission, even after this timestamp or during review; no extra cancellation period is guaranteed.
tracking_urlYes
address_statusYes
document_sourceYes
first_usps_scanYesEarliest recorded individual-letter USPS scan, including acceptance: at is UTC, date is the scan’s local YYYY-MM-DD date, scan is USPS’s wording. Excludes shipment acceptance-pending and printing-partner scans. Null means no individual-letter scan is recorded, not that the letter was never mailed. Only proof_of_mailing establishes an acceptance date.
tracking_numberYes
address_as_givenYes
files_deleted_atYesUTC time the letter files were deleted, or null. After deletion, preview_url is retained for compatibility but no longer downloads a file; receipt_url is omitted. Tracking and the record stay available at letter_url.
proof_of_mailingYesThe acceptance scan records when USPS accepted the letter; null until an acceptance scan is recorded. Assistants cite date as the mailing date. This is not a postmarked receipt or a legal-status determination.
partner_checked_atYesUTC time of the last successful live tracking poll recorded by this service, even if USPS supplied no new scans. Null means no successful poll time is recorded (including test or legacy letters). A read never polls the partner; this is not a delivery or mailing time or a freshness guarantee.
acceptance_expected_byYesEastern date (YYYY-MM-DD) by whose end the acceptance scan usually appears. Present from submission while no acceptance or individual-piece network/delivery scan is recorded and next_step gives this date. Null after an individual-piece scan even if acceptance is missing; proof_of_mailing remains null. Before it ends, tell the person when to contact support; after it ends, contact support now so we can check with the printing partner and USPS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare idempotent/destructive/open-world; the description goes well beyond them, spelling out conditional idempotency ("Idempotent while paid, screening or held for review; refused before payment or after submission or cancellation"); the scope of the side effect ("only the hold is skipped"); and the absence of time guarantees. It also tells the agent to read cancel_until and next_step afterward, which is real operational context.

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 the purpose and reasonably tight; the example and the next_step instruction both earn their place. Some sentences are telegraphic to the point of ambiguity ("Idempotent while paid, screening or held for review"), which costs a little clarity for the space saved.

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?

Output schema exists, so return-value documentation is not required, yet the description still points at cancel_until and next_step usefully. It covers auth, refusal conditions, side-effect bounds and idempotency. The main residual gap is that the relationship between id and letter_url (which to supply when, and what happens if both are given) is left implicit.

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, but the description adds two genuinely new constraints: id must go with the API key that created the letter, and the alternative is the complete private letter_url with its t token. The inline example clarifies the URL shape with its token query parameter, though the id/letter_url mutual exclusivity is only implied.

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 plus the exact scope: "Skip a paid letter's 30-minute cancellation hold when the person asks to send it right away." It immediately distinguishes itself from submission ("does not submit immediately") and from cancellation, so an agent can tell it apart from siblings like cancel_letter or create_letter.

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 clear triggering condition ("when the person asks to send it right away") and explicit limits on what it is not for ("never bypasses screening", "does not submit immediately"). Refusal states ("refused before payment or after submission or cancellation") tell the agent when the call will fail. It stops short of naming which sibling to use instead for cancelling or submitting.

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