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. U.S. destinations.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / transaction_state
      Added value: +{
      +  "description": "Always QUOTED: a price only, nothing exists yet.",
      +  "enum": [
      +    "QUOTED"
      +  ],
      +  "type": "string"
      +}
  2. 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."
  3. 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."
  4. 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"
      +]
  5. 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"
      +]
  6. 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"
      +]
  7. 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."
  8. First observed

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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources