Skip to main content
Glama

Check a letter before it is mailed

check_certified_letter
Read-onlyIdempotent

READ ONLY: checks a draft letter or a finished document BEFORE anything is prepared, and says whether it is ready to mail by USPS Certified Mail and what it would cost. Use it when the person asks "is this ready to send?", "check this before I mail it", "did I forget anything?", "is this ready for Certified Mail?", "should I send this with a return receipt?" or "what would it cost to send this certified?", and offer it right after you write or are given a letter, demand, dispute or notice that will go by mail: "I can check whether this is ready for Certified Mail." It returns the printed page count (the same layout the review page charges for), the document type it reads as, the recipient and sender it found and whether each address is complete, the missing fields, unfilled placeholders such as [NAME], enclosures the letter mentions, a reply-by date written in the letter, the recommended service with the exact current price, and the next action. It checks mailing readiness, never legal sufficiency. It creates nothing, stores nothing, prints, mails and charges nothing, and needs no account. When it says ready_to_prepare, fix nothing else: quote_certified_letter gives other prices, and prepare_certified_letter with the same text and addresses creates the review link once the person wants it sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
stateNoTwo-letter U.S. state code.
subjectNoThe "Re:" line, if any.
letter_textNoThe letter body as it would print: salutation, paragraphs and closing, without the addresses or date (those come from the other fields). Up to 60,000 characters. Pass this OR document_text.
postal_codeNoFive-digit ZIP code.
sender_cityNo
sender_nameNo
sender_stateNo
address_line1NoRecipient street address.
address_line2No
document_textNoThe full text of a document that is already finished and prints exactly as written, addresses and signature included. Up to 60,000 characters. Pass this OR letter_text.
recipient_nameNo
signature_nameNoName printed under the closing.
desired_serviceNoThe service the person has in mind, if any; its price is returned as current_estimated_price. Left out, the recommended service is priced.
recipient_companyNo
sender_postal_codeNo
enclosures_suppliedNoNames of enclosures the person says they have, so an enclosure the letter mentions is not reported missing.
sender_address_blockNoThe sender (return address) as written, one part per line.
sender_address_line1No
recipient_address_blockNoThe recipient as addressed, one part per line. Named recipient fields win over it. Left out, the recipient is read from the inside address in the text, if it has one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
mailedYesAlways false.
storedYesAlways false: nothing from this call is kept.
chargedYesAlways false.
warningsNo
max_pagesNo
promotionNoPresent when the first-letter promotion could lower this total; the review page applies it once the account is known.
next_actionYes
document_typeNo
missing_fieldsYes
detected_senderNo
ready_to_prepareYesTrue when nothing blocks mailing: the recipient address is complete, nothing is left to fix and the length fits the printer.
prices_by_serviceNo
deadline_in_letterNo
detected_recipientNo
document_type_labelNo
recommended_becauseNo
recommended_serviceYes
estimated_page_countYes
current_estimated_priceNoThe exact current total for desired_service, or for the recommended service.
requires_human_approvalNo
sender_address_completeNoThe sender can also be filled in on the review page, so an incomplete sender does not block preparing.
recipient_read_from_textNo
recipient_address_completeNo
potential_deadline_detectedNoTrue when the letter itself asks for an answer, payment or action by a date or within a number of days. Read from the text; it is not a legal deadline determination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: it creates, stores, prints, mails and charges nothing, needs no account, and explicitly scopes itself to mailing readiness rather than legal sufficiency. It also enumerates the returned signals, which is a meaningful behavioral disclosure.

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?

Long but front-loaded and dense: the READ ONLY marker, the check, and the routing alternative all appear early, and no sentence is filler. Slight repetition of routing instructions keeps it from a 5.

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 20-param read-only check with an output schema and full annotations, the description covers timing, safety, return contents, and sibling routing. Nothing an agent needs to call it correctly is missing.

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 coverage is 55% and the description mostly describes behavior rather than clarifying individual fields (letter_text vs document_text, sender_address_block precedence, enclosures_supplied). It hints at the recipient/sender reading logic but leaves the parameter-level distinctions to the schema, which only partially documents them.

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+resource (check a certified letter) with scope (draft or finished document, before anything is prepared) and clearly demarcates it from quote_certified_letter and prepare_certified_letter by name. An agent can distinguish it from every sibling.

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?

Gives explicit trigger phrases ('is this ready to send?', 'what would it cost to send this certified?') and a proactive-offer instruction right after a letter is written. It also names the alternatives and the exact condition ('when it says ready_to_prepare') that routes to quote or prepare.

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