Skip to main content
Glama

Price a certified letter

quote_certified_letter
Read-onlyIdempotent

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, or check_certified_letter first to check a draft and price it by its real page count. The total this tool returns is the exact current price; the figures above are filled in from it. U.S. destinations.

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

Input 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

NameRequiredDescriptionDefault
totalYesThe same total, formatted for a person, with a dollar sign and cents.
mailedYesAlways false: this tool never mails.
chargedYesAlways false: this tool never charges.
serviceYes
currencyYes
promotionNoPresent when the first-letter promotion could lower this total for a person’s first letter. It is applied by the same rule on the review page and in authorize_certified_letter once the payer is known; total_cents is the standard price and is what to quote until then.
page_countYes
total_centsYesThe whole price in cents. Nothing else is added at checkout.
price_sourceNo
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / promotion / description
      Previous value: -"Present when the first-letter promotion could lower this total for a person’s first letter. The review page applies it once the account is known; total_cents is the standard price."New value: +"Present when the first-letter promotion could lower this total for a person’s first letter. It is applied by the same rule on the review page and in authorize_certified_letter once the payer is known; total_cents is the standard price and is what to quote until then."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / price_source
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / promotion
      Added value: +{
      +  "description": "Present when the first-letter promotion could lower this total for a person’s first letter. The review page applies it once the account is known; total_cents is the standard price.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / total / description
      Previous value: -"The same total, formatted for a person, e.g. \"$16.17\"."New value: +"The same total, formatted for a person, with a dollar sign and cents."
  3. Changed1 schema field changed
    • addedOutput schema / properties / transaction_state
      Added value: +{
      +  "description": "Always QUOTED: a price only, nothing exists yet.",
      +  "enum": [
      +    "QUOTED"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema 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. Changed1 schema 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. Changed3 schema 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. Changed2 schema 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. Changed2 schema 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. Changed1 schema 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. Added

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the safety bar is covered. The description still adds useful behavior: that the total is all-in with nothing added at checkout, that a person's first letter is $9.95 once per account, that no account or subscription is required, and that the returned total is the exact current price. The 'prepares nothing, stores nothing' prose partly restates the readOnly annotation, which keeps it from a 5.

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 trigger condition and the read-only scope are front-loaded, and nothing is buried. It is long, though: the four-tier price table duplicates information the tool itself returns, and the closing sentence acknowledging that the figures are 'filled in from' the returned total is a slightly awkward hedge on numbers that could go stale.

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?

With an output schema present, the description does not need to explain return format, and it covers everything else: the trigger, the defaults, the pricing model, the first-letter exception, what the tool does not do, and when to hand off to the sibling tools. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum descriptions already define each service tier in detail, so the schema does most of the work. The description still adds meaning by mapping each tier to a concrete price ($12.97 / $15.97 / $24.21 / $50.10), confirming that CERTIFIED_ERR is the default, and telling the caller to supply the printed page count that drives the price.

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 and resource: it says what a USPS Certified Mail letter costs, before anything is prepared. It distinguishes itself from siblings by naming prepare_certified_letter and check_certified_letter and describing their different roles.

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 ('when the person asks what it costs... or is weighing sending it themselves'), names the alternatives, and states the condition that selects each one: use prepare_certified_letter once the person wants it sent, or check_certified_letter to price a draft by its real page count. There is also a clear scope limit: U.S. destinations.

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