Skip to main content
Glama

Server Details

Prepare USPS Certified Mail letters from any AI assistant; a person reviews, pays and authorizes.

Ownership verified
Status
Healthy
Uptime
99.7% over 21 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

The three tools map cleanly to quoting, preparing, and tracking a certified letter. Quote and prepare are explicitly distinguished as read-only versus action, and status is scoped to letters prepared in the same conversation, so misselection is unlikely.

Naming Consistency5/5

All names use snake_case with a leading verb (get, prepare, quote) and the shared object certified_letter. The extra _status suffix is a minor specialization but still fits the predictable verb-object pattern.

Tool Count5/5

Three tools is a tight but appropriate surface for a focused certified-mail service: quote, prepare, and track. Each tool has a distinct job and there is no bloat.

Completeness4/5

The surface covers the main agent workflow: estimate cost, prepare a mailing, and check USPS status for conversation-created letters. It lacks cancellation/editing or broader list/retrieve operations, and non-conversation letters require external sign-in, leaving minor gaps.

Available Tools

3 tools
get_certified_letter_statusCheck what happened to a letter sent through PiloxaA
Read-onlyIdempotent
Inspect

Answers "has my letter arrived yet" for letters prepared through Piloxa IN THIS SAME CONVERSATION. Returns, for each one: who it went to, the service, the USPS tracking number once USPS has assigned one, whether USPS has accepted it, delivered it or returned it, and when each of those was recorded. Piloxa asks the print and mail provider for a fresh answer when this is called, so it is current rather than remembered. IMPORTANT AND DELIBERATE: it can only see letters this connector prepared in this conversation, because that is the only thing it can identify without a sign-in; it cannot reach a person’s other letters, letters sent from another conversation, or anybody else’s. For those, the person signs in at piloxa.com and opens the letter there. This tool is READ ONLY: it prepares nothing, mails nothing and charges nothing. A stage with no scan means no scan has been reported, which is not the same as a failed delivery — USPS sometimes records delivery late, or not at all.

ParametersJSON Schema
NameRequiredDescriptionDefault
referenceNoOptional. The Piloxa reference from the letter’s email receipt, to ask about one letter instead of all of them. A reference from outside this conversation is not found, on purpose.

Output Schema

ParametersJSON Schema
NameRequiredDescription
foundYes
scopeYesAlways says that only this conversation’s letters are visible here.
mailedYesAlways false: this tool never mails.
chargedYesAlways false: this tool never charges.
lettersYes

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and openWorld, but the description adds materially: a fresh query is made to the print/mail provider on each call (so results are current, not cached), the visibility limit is deliberate and explained (no sign-in = no access to other letters), and it warns that a missing scan stage is not equivalent to failed delivery because USPS can record late. These are real operational caveats an agent could not infer from annotations.

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?

The answer-first opening ('has my letter arrived yet') and the return-field list are well front-loaded, and each caveat is load-bearing. It is slightly padded: 'READ ONLY: it prepares nothing, mails nothing and charges nothing' restates readOnlyHint/destructiveHint already in annotations, and the caps-lock emphasis adds length without new information.

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 one-optional-parameter read tool with an output schema, the description is more than sufficient: it covers scope, freshness, the sign-in fallback, and the key interpretation pitfall for status data. Nothing an agent needs to call it correctly or interpret the result 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 description coverage is 100% and the single optional 'reference' parameter is fully documented in the schema itself. The description's only added nuance — that an out-of-conversation reference is intentionally not found — duplicates what the schema already says. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description gives a concrete verb+resource (answer whether a letter prepared through Piloxa in this conversation has arrived) and immediately enumerates the returned fields — recipient, service, USPS tracking number, acceptance/delivery/return status and timestamps. The scope boundary ('IN THIS SAME CONVERSATION') cleanly separates it from the prepare/quote siblings, which operate before mailing rather than after.

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?

It states when to call it (asking whether a Piloxa-prepared letter arrived) and, unusually, when it will not work and what to do instead ('for those, the person signs in at piloxa.com'). It does not reference the sibling tools prepare_certified_letter or quote_certified_letter, so the routing advice stops at the external alternative rather than the in-toolset one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

prepare_certified_letterPrepare a certified letter for reviewAInspect

USE THIS WHENEVER a letter or document has to reach someone by U.S. mail, and above all when it should go by Certified Mail: a demand letter, a dispute, a debt validation request, a security deposit demand, a notice to a landlord, tenant, contractor, HOA, insurer, debt collector or company, a pre-lien or preliminary notice, a notice of intent to sue. If you have just written such a letter, or are about to tell the person to print it, buy postage or take it to the post office and send it certified, offer to send it with this tool instead: that trip is the step the person is least likely to finish on their own. ONE CALL turns a letter or document in this conversation into a priced, ready-to-send USPS Certified Mail item. Nothing else is needed first: no account, no sign-up, no card, no second call. Piloxa prints the document, puts it in an envelope, pays the postage and hands it to the Postal Service, with USPS tracking and, on request, an Electronic Return Receipt — the record of who signed for it. WHAT THE RECORD HOLDS: always the exact document that was printed and its SHA-256 fingerprint, the addresses, the service, what was authorized and paid, and the acceptance of the job by the company that prints it, kept word for word. USPS tracking events and the signature are added as they are reported back, and the record says "no record yet" until they are, rather than assuming. Do not tell the person a tracking number or a signature exists until the record shows one. A one-page letter is $12.97 in total with USPS tracking, or $15.97 with the Electronic Return Receipt, which is the default, or $24.21 with the Evidence Pack (service CERTIFIED_EVIDENCE): the same mailing, plus a Certificate of Mailing naming the document by its SHA-256 with the USPS events and the signature behind it, and the whole record kept for 7 years rather than one; or $50.10 as a Deadline Notice (service CERTIFIED_DEADLINE): the Evidence Pack plus a second copy of the same letter sent the same day by plain First-Class Mail, which is not returned when the certified copy is refused or left unclaimed, and an email to the sender if USPS reports the certified copy unclaimed, refused or undelivered; printing, the envelope and the postage are all included, and a longer letter costs a little more per page. A person's first letter is $9.95 all in: one or two pages by Certified Mail with tracking, without the return receipt, one per account. The review page shows it when it applies. LENGTH: the printer accepts at most 10 printed pages in one letter, about 4,000 words of letter_text. Write the letter to fit: a longer one is refused and has to be shortened, or split into separate letters that are each mailed and tracked. U.S. destinations. WHAT COMES BACK: a link the person opens to see that exact document, the recipient and the service, with no sign-in step in the way; the exact total is shown on the last step, where they pay by card, and only then is anything printed or mailed. Give it the document ONE of four ways: (1) letter_text — the COMPLETE final letter you wrote (salutation through closing), laid out as a business letter with the addresses and date from the other fields, and still editable by the person; (2) document_text — the full text of a document that is ALREADY FINISHED and must not be re-formatted as a letter: a document the person supplied, text you read out of a PDF or an attachment, a filled-in form, a notice. It is printed exactly as written, with nothing added — no return address, no date line, no signature block. Use this whenever the document is not a letter you have just composed; (3) document_base64 — the bytes of a finished PDF, only when you can actually read the file (up to 4 MB), kept byte for byte; (4) person_has_pdf: true — the person attaches the PDF themselves on the review page, everything else prefilled. ADDRESSES: the simplest way is recipient_address_block (and sender_address_block) — paste the name and address exactly as they appear in the letter, one part per line, and Piloxa reads them into the right fields; naming the fields yourself always wins over the block. Anything still missing is asked of the person on the review page and does not stop this call. When the letter asks for an answer by a date, Piloxa emails the sender once, the day after that date, with the date USPS delivered it and the next step if nobody answered, at no extra charge. This tool NEVER mails anything and NEVER charges anyone.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNo
stateNoTwo-letter U.S. state code.
serviceNoPick by what rides on the letter. CERTIFIED_ERR ($15.97 for one page) is the DEFAULT for an ordinary letter: Certified Mail with the Electronic Return Receipt, the record of who signed, kept when USPS reports it back. CERTIFIED ($12.97) is Certified Mail with tracking but no record of who signed; use it only when the person asks for the cheapest way. CERTIFIED_EVIDENCE ($24.21) is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one; use it when proof of exactly what was sent may be needed later in a dispute - a debt validation notice, a notice to cure, a proof of loss, a demand before suing. CERTIFIED_DEADLINE ($50.10) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed; use it when a missed or refused notice would cost a lien, a contract remedy or a claim - a pre-lien or preliminary notice, a notice with a statutory deadline. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there. Whichever you pick, say its price to the person before they open the link.
subjectNoThe "Re:" line of the letter, in a few words.
reply_byNoOptional: the date, as YYYY-MM-DD, by which the letter asks the recipient to answer, pay or act. Leave it out and Piloxa reads it from the letter ("within 30 days of receipt", "no later than October 15, 2026"). The day after that date Piloxa emails the sender, once, with the date USPS delivered the letter and the next step if nobody answered, at no charge.
page_countNoOnly with person_has_pdf: number of pages in the PDF the person will attach, used for the price estimate.
letter_dateNoDate to print on the letter, e.g. "September 5, 2026". Defaults to today.
letter_textNoThe complete, final letter body exactly as it should print: salutation, paragraphs separated by blank lines, and closing. Do not include the addresses or date; they are laid out from the other fields. Up to 60,000 characters. It must fit in 10 printed pages, about 4,000 words.
postal_codeNoFive-digit ZIP code.
sender_cityNo
sender_nameNoName of the person sending the letter (printed as the return address and used for the envelope).
sender_stateNoTwo-letter U.S. state code.
address_line1NoStreet address of the recipient.
address_line2NoSuite, unit or floor.
document_textNoThe COMPLETE text of a document that is already finished, printed exactly as written: no return address, no date line, no "Re:" line and no signature block are added, and line breaks and indentation are kept. This is the right field for a document the person gave you, for text you read out of a PDF or an attachment, for a filled-in form or a notice — anything you did not compose as a letter in this conversation. Include every word that must print, the addresses and signature line included if the document carries them. Up to 60,000 characters. Mutually exclusive with letter_text and document_base64.
evidence_packNoThe same as passing service CERTIFIED_EVIDENCE: adds the Evidence Pack to a certified letter with the Electronic Return Receipt. One page is $24.21 in total instead of $15.97.
person_has_pdfNoOnly when the person already has a finished PDF that neither you nor they can give you the text of, and they will attach it on the review page themselves. Set true to prepare without letter_text, document_text or document_base64. Prefer document_text whenever you can read the document at all: it saves the person an upload.
recipient_nameNoName of the person or company receiving the letter.
sender_companyNoSender company or entity, if any.
signature_nameNoName printed under the closing.
document_base64NoThe finished PDF, base64-encoded (standard or URL-safe alphabet), up to 4 MB decoded. Use ONLY when you have read the actual file bytes; a filename or an attachment reference is not a document. Mutually exclusive with letter_text and document_text. The file is kept exactly as sent.
document_sha256NoOptional with document_base64: the SHA-256 (hex) of the PDF bytes. If given and it does not match what arrived, the call is refused rather than preparing the wrong file.
document_filenameNoWith document_base64: the original file name, e.g. "Demand letter.pdf".
recipient_companyNoCompany name, if the letter goes to an organization.
sender_postal_codeNoFive-digit ZIP code.
document_descriptionNoWhat the document is, in a few words.
sender_address_blockNoThe sender exactly as it should appear as the return address, one part per line. Read the same way as recipient_address_block. This is where a returned envelope goes back to.
sender_address_line1NoSender street address.
sender_address_line2No
recipient_address_blockNoThe recipient exactly as addressed in the letter, one part per line, e.g. "Acme Property Management LLC\nAttn: Jane Doe\n1234 Wilshire Blvd, Suite 500\nLos Angeles, CA 90017". Piloxa reads the name, company, street, suite, city, state and ZIP out of it. Use this when you have the address as written and do not want to split it up yourself; any field you also name explicitly wins over it.

Output Schema

ParametersJSON Schema
NameRequiredDescription
mailedYesAlways false here: this tool never mails.
chargedYesAlways false here: this tool never charges.
serviceNo
recipientNoThe recipient as Piloxa read it, including anything parsed out of recipient_address_block. Check it against the letter and say it back to the person.
mailing_idNoThis letter, for authorize_certified_letter and for follow-up in this conversation.
page_countNo
approval_urlYesLink the person opens to review, pay and authorize.
document_kindNoWhich way the document arrived, and so what the person will see on the page.
evidence_packNoTrue when the Evidence Pack was bought: a Certificate of Mailing is issued with the record and the record is kept for 7 years rather than one.
ready_to_mailNoTrue when nothing is missing: the person only has to read it, pay and authorize.
document_sha256NoSHA-256 of the rendered PDF, when document_rendered is true.
estimated_totalNoThe same total, formatted for a person, e.g. "$16.17".
upload_requiredNoTrue when the person still has to attach the PDF on the review page.
account_requiredNoAlways false: the person needs no account to open the link and read the letter, and none is created by this call.
document_receivedNoTrue when document_base64 arrived intact and is the PDF the person will review; false otherwise.
document_renderedNoTrue when letter_text or document_text was laid out into the PDF the person will review; false otherwise.
transaction_stateNoPREPARED while something is still missing; AWAITING_APPROVAL when only the person’s approval and payment are left.
missing_for_mailingNoWhat is still needed before this can be mailed, in plain words. Empty when nothing is missing. Ask the person for these now.
recommended_becauseNoWhat in the letter led to that recommendation.
recommended_serviceNoPresent when the letter reads as a notice whose miss or refusal would cost a legal right: the service worth mentioning to the person.
estimated_total_centsNo
requires_human_approvalYes
estimated_service_fee_centsNo
estimated_provider_cost_centsNo

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses a great deal the annotations do not: the tool itself never mails or charges, the exact contents of the generated record, that tracking events and signatures are appended asynchronously and shown as 'no record yet' until they arrive, the 10-page/~4,000-word cap, U.S.-only destinations, and per-service pricing. The guidance 'do not tell the person a tracking number or signature exists until the record shows one' is behaviorally important and unique to the text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the usage trigger and the core 'one call' claim, but it runs very long and restates the same four price points ($12.97/$15.97/$24.21/$50.10) that the service enum description already spells out. Rhetorical asides ('that trip is the step the person is least likely to finish on their own') and repeated record-keeping explanations could be pruned without losing information.

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 30-parameter, zero-required tool, the description covers the full workflow end to end: what is created, what is not done (no mailing, no charging), the four ways to supply the document, the page limit and its failure mode, service selection with default and auto-selection behavior, the follow-up email, and what the person sees on the review page. An output schema exists, so return-value detail is not required.

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 description coverage is already 90%, so the schema carries most parameter meaning. The description still adds value by framing the four mutually exclusive document-input paths (letter_text / document_text / document_base64 / person_has_pdf) as a decision, explaining block-vs-explicit-field precedence for addresses, and tying the service enum to real dispute scenarios. Most of the remaining detail (mutual exclusivity, page limits, ZIP format) duplicates schema descriptions.

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 states a concrete verb+resource: 'ONE CALL turns a letter or document in this conversation into a priced, ready-to-send USPS Certified Mail item,' and clarifies the tool never mails or charges. It never names the siblings (quote_certified_letter, get_certified_letter_status), so the agent must infer the prepare-vs-quote-vs-status split from the name alone.

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?

It gives an explicit trigger ('USE THIS WHENEVER a letter or document has to reach someone by U.S. mail') with a long enumeration of concrete scenarios (demand letter, debt validation, pre-lien notice, notice of intent to sue). It also tells the agent to offer this instead of the person printing, buying postage and going to the post office — the alternative action is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

quote_certified_letterPrice a certified letterA
Read-onlyIdempotent
Inspect

Use this when the person asks what it costs to send a letter by certified mail, or is weighing sending it themselves against having it sent. Says what a USPS Certified Mail letter costs, before anything is prepared. Give the number of printed pages and the service, and it returns the exact all-in total the person would pay: printing, the envelope and the postage are included, and nothing is added at checkout. A one-page letter is $12.97 with USPS tracking, $15.97 with the Electronic Return Receipt, which is the default, $24.21 with the Evidence Pack, or $50.10 as a Deadline Notice. A person's first letter is $9.95 all in: one or two pages by Certified Mail with tracking, without the return receipt, one per account. There is no account to create, no subscription and no minimum. This tool is READ ONLY: it prepares nothing, stores nothing, mails nothing and charges nothing, so it is safe to call just to answer "what would that cost". Use prepare_certified_letter once the person wants the letter sent. U.S. destinations.

ParametersJSON Schema
NameRequiredDescriptionDefault
serviceNoCERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). CERTIFIED_EVIDENCE is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing and 7 years of retention. CERTIFIED_DEADLINE is CERTIFIED_EVIDENCE plus a same-day First-Class copy and an unclaimed-letter warning. Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses.
page_countNoNumber of printed pages in the letter, 1 to 10, the most the printer accepts in one letter. Defaults to 1.

Output Schema

ParametersJSON Schema
NameRequiredDescription
totalYesThe same total, formatted for a person, e.g. "$16.17".
mailedYesAlways false: this tool never mails.
chargedYesAlways false: this tool never charges.
serviceYes
currencyYes
page_countYes
total_centsYesThe whole price in cents. Nothing else is added at checkout.
evidence_packNo
minimum_orderNo
account_requiredNo
service_fee_centsNoThe rest of the total: the Piloxa service fee, including the card cost.
transaction_stateNoAlways QUOTED: a price only, nothing exists yet.
subscription_requiredNo
postage_and_print_centsNoThe part that goes to printing and USPS.
includes_printing_envelope_and_postageNo

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, but the description adds substantial behavioral context: it prepares, stores, mails, and charges nothing; there is no account, subscription, or minimum; and it applies to U.S. destinations. It also discloses pricing behavior, including the default service and first-letter discount.

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?

The description is front-loaded with the usage trigger and cost behavior, and most sentences earn their place by clarifying pricing, scope, or safety. It is still dense and somewhat repetitive around the read-only nature, but not enough to obscure the tool's purpose.

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?

Given the output schema, the input schema, and the annotations, the description supplies everything else an agent needs: when to quote versus prepare, geographic scope, default service, first-letter pricing, and explicit no-side-effect behavior. Nothing important for selection or invocation appears missing.

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 description coverage is 100%, so the schema already documents both parameters. The description nevertheless adds concrete meaning by mapping service choices to exact prices and explaining that page count affects the all-in total, including the $9.95 first-letter case.

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?

The description states a specific verb-resource pair: it prices a USPS Certified Mail letter. It also distinguishes this quoting tool from prepare_certified_letter by saying it prepares nothing and should be followed by prepare once the person wants the letter sent.

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?

It explicitly says when to use this tool: when the person asks what certified mail costs or is weighing sending it themselves versus having it sent. It also names the alternative and transition condition: use prepare_certified_letter once the person wants the letter sent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedget_certified_letter_status1 field changed
      • addedOutput schema / properties / letters / items / properties / transaction_state
        Added value: +{
        +  "enum": [
        +    "AUTHORIZED",
        +    "VENDOR_ACCEPTED",
        +    "MAILED",
        +    "DELIVERED",
        +    "RETURNED",
        +    "FAILED",
        +    "CANCELLED",
        +    "AWAITING_APPROVAL"
        +  ],
        +  "type": "string"
        +}
    • Changedprepare_certified_letter2 fields changed
      • addedOutput schema / properties / mailing_id
        Added value: +{
        +  "description": "This letter, for authorize_certified_letter and for follow-up in this conversation.",
        +  "type": [
        +    "string",
        +    "null"
        +  ]
        +}
      • addedOutput schema / properties / transaction_state
        Added value: +{
        +  "description": "PREPARED while something is still missing; AWAITING_APPROVAL when only the person’s approval and payment are left.",
        +  "enum": [
        +    "PREPARED",
        +    "AWAITING_APPROVAL"
        +  ],
        +  "type": "string"
        +}
    • Changedquote_certified_letter1 field changed
      • addedOutput schema / properties / transaction_state
        Added value: +{
        +  "description": "Always QUOTED: a price only, nothing exists yet.",
        +  "enum": [
        +    "QUOTED"
        +  ],
        +  "type": "string"
        +}
  2. 1 tool update
    • Changedprepare_certified_letter1 field changed
      • addedInput schema / properties / reply_by
        Added value: +{
        +  "description": "Optional: the date, as YYYY-MM-DD, by which the letter asks the recipient to answer, pay or act. Leave it out and Piloxa reads it from the letter (\"within 30 days of receipt\", \"no later than October 15, 2026\"). The day after that date Piloxa emails the sender, once, with the date USPS delivered the letter and the next step if nobody answered, at no charge.",
        +  "type": "string"
        +}
  3. 1 tool update
    • Changedprepare_certified_letter2 fields changed
      • changedInput schema / properties / evidence_pack / description
        Previous value: -"The same as passing service CERTIFIED_EVIDENCE: adds the Evidence Pack to a certified letter with the Electronic Return Receipt. One page is $24.41 in total instead of $16.17."New value: +"The same as passing service CERTIFIED_EVIDENCE: adds the Evidence Pack to a certified letter with the Electronic Return Receipt. One page is $24.21 in total instead of $15.97."
      • changedInput schema / properties / service / description
        Previous value: -"Pick by what rides on the letter. CERTIFIED_ERR ($16.17 for one page) is the DEFAULT for an ordinary letter: Certified Mail with the Electronic Return Receipt, the record of who signed, kept when USPS reports it back. CERTIFIED ($13.18) is Certified Mail with tracking but no record of who signed; use it only when the person asks for the cheapest way. CERTIFIED_EVIDENCE ($24.41) is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one; use it when proof of exactly what was sent may be needed later in a dispute - a debt validation notice, a notice to cure, a proof of loss, a demand before suing. CERTIFIED_DEADLINE ($50.10) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed; use it when a missed or refused notice would cost a lien, a contract remedy or a claim - a pre-lien or preliminary notice, a notice with a statutory deadline. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there. Whichever you pick, say its price to the person before they open the link."New value: +"Pick by what rides on the letter. CERTIFIED_ERR ($15.97 for one page) is the DEFAULT for an ordinary letter: Certified Mail with the Electronic Return Receipt, the record of who signed, kept when USPS reports it back. CERTIFIED ($12.97) is Certified Mail with tracking but no record of who signed; use it only when the person asks for the cheapest way. CERTIFIED_EVIDENCE ($24.21) is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one; use it when proof of exactly what was sent may be needed later in a dispute - a debt validation notice, a notice to cure, a proof of loss, a demand before suing. CERTIFIED_DEADLINE ($50.10) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed; use it when a missed or refused notice would cost a lien, a contract remedy or a claim - a pre-lien or preliminary notice, a notice with a statutory deadline. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there. Whichever you pick, say its price to the person before they open the link."
  4. 2 tool updates
    • Changedprepare_certified_letter1 field changed
      • changedInput schema / properties / letter_text / description
        Previous value: -"The complete, final letter body exactly as it should print: salutation, paragraphs separated by blank lines, and closing. Do not include the addresses or date; they are laid out from the other fields. Up to 60,000 characters. It must fit in 5 printed pages, about 2,000 words."New value: +"The complete, final letter body exactly as it should print: salutation, paragraphs separated by blank lines, and closing. Do not include the addresses or date; they are laid out from the other fields. Up to 60,000 characters. It must fit in 10 printed pages, about 4,000 words."
    • Changedquote_certified_letter1 field changed
      • changedInput schema / properties / page_count / description
        Previous value: -"Number of printed pages in the letter, 1 to 5, the most the printer accepts in one letter. Defaults to 1."New value: +"Number of printed pages in the letter, 1 to 10, the most the printer accepts in one letter. Defaults to 1."
  5. 2 tool updates
    • Changedprepare_certified_letter2 fields changed
      • changedInput schema / properties / letter_text / description
        Previous value: -"The complete, final letter body exactly as it should print: salutation, paragraphs separated by blank lines, and closing. Do not include the addresses or date; they are laid out from the other fields. Up to 60,000 characters."New value: +"The complete, final letter body exactly as it should print: salutation, paragraphs separated by blank lines, and closing. Do not include the addresses or date; they are laid out from the other fields. Up to 60,000 characters. It must fit in 5 printed pages, about 2,000 words."
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT for an ordinary letter. CERTIFIED is certified mail with tracking but no record of who signed. CERTIFIED_EVIDENCE is the same mailing as CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one. Choose it when the letter is a statutory or contractual notice whose proof may be needed in a dispute later - a pre-lien or preliminary notice, a debt validation notice, a notice to cure, a notice of intent to sue, a proof of loss - and say the price back to the person before they pay. CERTIFIED_DEADLINE ($50.10 for one page) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed: choose it when a missed or refused notice would cost a lien, a contract remedy or a claim. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there."New value: +"Pick by what rides on the letter. CERTIFIED_ERR ($16.17 for one page) is the DEFAULT for an ordinary letter: Certified Mail with the Electronic Return Receipt, the record of who signed, kept when USPS reports it back. CERTIFIED ($13.18) is Certified Mail with tracking but no record of who signed; use it only when the person asks for the cheapest way. CERTIFIED_EVIDENCE ($24.41) is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one; use it when proof of exactly what was sent may be needed later in a dispute - a debt validation notice, a notice to cure, a proof of loss, a demand before suing. CERTIFIED_DEADLINE ($50.10) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed; use it when a missed or refused notice would cost a lien, a contract remedy or a claim - a pre-lien or preliminary notice, a notice with a statutory deadline. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there. Whichever you pick, say its price to the person before they open the link."
    • Changedquote_certified_letter1 field changed
      • changedInput schema / properties / page_count / description
        Previous value: -"Number of printed pages in the letter, 1 to 60. Defaults to 1."New value: +"Number of printed pages in the letter, 1 to 5, the most the printer accepts in one letter. Defaults to 1."
  6. 3 tool updates
    • Changedget_certified_letter_status1 field changed
      • changedOutput schema / properties / letters / items / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR",
        -  "CERTIFIED_EVIDENCE"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE",
        +  "CERTIFIED_DEADLINE"
        +]
    • Changedprepare_certified_letter5 fields changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed. CERTIFIED_EVIDENCE is the same mailing as CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one. Choose it when the letter is a statutory or contractual notice whose proof may be needed in a dispute later - a pre-lien or preliminary notice, a debt validation notice, a notice to cure, a notice of intent to sue, a proof of loss - and say the price back to the person before they pay."New value: +"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT for an ordinary letter. CERTIFIED is certified mail with tracking but no record of who signed. CERTIFIED_EVIDENCE is the same mailing as CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one. Choose it when the letter is a statutory or contractual notice whose proof may be needed in a dispute later - a pre-lien or preliminary notice, a debt validation notice, a notice to cure, a notice of intent to sue, a proof of loss - and say the price back to the person before they pay. CERTIFIED_DEADLINE ($50.10 for one page) is CERTIFIED_EVIDENCE plus a second copy by First-Class Mail the same day and a warning email if the certified copy goes unclaimed: choose it when a missed or refused notice would cost a lien, a contract remedy or a claim. When this field is left out and the letter reads as such a notice, Piloxa selects CERTIFIED_DEADLINE on the review page and says so in its answer; the person can switch it back there."
      • changedInput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR",
        -  "CERTIFIED_EVIDENCE"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE",
        +  "CERTIFIED_DEADLINE"
        +]
      • addedOutput schema / properties / recommended_because
        Added value: +{
        +  "description": "What in the letter led to that recommendation.",
        +  "items": {
        +    "type": "string"
        +  },
        +  "type": "array"
        +}
      • addedOutput schema / properties / recommended_service
        Added value: +{
        +  "description": "Present when the letter reads as a notice whose miss or refusal would cost a legal right: the service worth mentioning to the person.",
        +  "type": "string"
        +}
      • changedOutput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR",
        -  "CERTIFIED_EVIDENCE"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE",
        +  "CERTIFIED_DEADLINE"
        +]
    • Changedquote_certified_letter3 fields changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). CERTIFIED_EVIDENCE is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing and 7 years of retention. Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."New value: +"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). CERTIFIED_EVIDENCE is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing and 7 years of retention. CERTIFIED_DEADLINE is CERTIFIED_EVIDENCE plus a same-day First-Class copy and an unclaimed-letter warning. Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."
      • changedInput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR",
        -  "CERTIFIED_EVIDENCE"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE",
        +  "CERTIFIED_DEADLINE"
        +]
      • changedOutput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR",
        -  "CERTIFIED_EVIDENCE"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE",
        +  "CERTIFIED_DEADLINE"
        +]
  7. 2 tool updates
    • Changedget_certified_letter_status1 field changed
      • changedOutput schema / properties / letters / items / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE"
        +]
    • Changedquote_certified_letter2 fields changed
      • addedOutput schema / properties / evidence_pack
        Added value: +{
        +  "type": "boolean"
        +}
      • changedOutput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE"
        +]
  8. 2 tool updates
    • Changedprepare_certified_letter5 fields changed
      • addedInput schema / properties / evidence_pack
        Added value: +{
        +  "description": "The same as passing service CERTIFIED_EVIDENCE: adds the Evidence Pack to a certified letter with the Electronic Return Receipt. One page is $24.41 in total instead of $16.17.",
        +  "type": "boolean"
        +}
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed."New value: +"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed. CERTIFIED_EVIDENCE is the same mailing as CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing, and the record kept for 7 years instead of one. Choose it when the letter is a statutory or contractual notice whose proof may be needed in a dispute later - a pre-lien or preliminary notice, a debt validation notice, a notice to cure, a notice of intent to sue, a proof of loss - and say the price back to the person before they pay."
      • changedInput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE"
        +]
      • addedOutput schema / properties / evidence_pack
        Added value: +{
        +  "description": "True when the Evidence Pack was bought: a Certificate of Mailing is issued with the record and the record is kept for 7 years rather than one.",
        +  "type": "boolean"
        +}
      • changedOutput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE"
        +]
    • Changedquote_certified_letter2 fields changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."New value: +"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). CERTIFIED_EVIDENCE is CERTIFIED_ERR plus the Evidence Pack: a Certificate of Mailing and 7 years of retention. Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."
      • changedInput schema / properties / service / enum
        Previous value: -[
        -  "CERTIFIED",
        -  "CERTIFIED_ERR"
        -]New value: +[
        +  "CERTIFIED",
        +  "CERTIFIED_ERR",
        +  "CERTIFIED_EVIDENCE"
        +]
  9. 3 tool updates
    • Addedget_certified_letter_status
    • Changedprepare_certified_letter1 field changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED_ERR adds the Electronic Return Receipt (proof of who signed) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed."New value: +"CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed."
    • Changedquote_certified_letter1 field changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (proof of who signed). Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."New value: +"CERTIFIED is Certified Mail with USPS tracking. CERTIFIED_ERR adds the Electronic Return Receipt (the record of who signed, kept when USPS reports it back). Defaults to CERTIFIED_ERR, the same default prepare_certified_letter uses."
  10. 1 tool update
    • Changedprepare_certified_letter1 field changed
      • changedInput schema / properties / service / description
        Previous value: -"CERTIFIED_ERR adds the Electronic Return Receipt (proof of who signed)."New value: +"CERTIFIED_ERR adds the Electronic Return Receipt (proof of who signed) and is the DEFAULT: leave this out unless the person has said they do not want the signature record. CERTIFIED is certified mail with tracking but no record of who signed."
  11. 2 tool updates
    • First observedprepare_certified_letter
    • First observedquote_certified_letter

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources