Skip to main content
Glama

Certified Mail Sender

Quote a certified letter

quote_letter
Read-only

Get an itemized price for 1-10 pages or count a base64 PDF. Quoting is free. Unknown input fields are rejected with invalid_request; error.fix names each unknown field and the accepted fields. For a return receipt, use service certified_err. One page costs $9.04 for certified or $12.24 with an electronic Return Receipt; use quote_letter for the exact page count. Quoting never creates, pays for or mails a letter. No refund once USPS accepts the letter, even if USPS can't deliver it. If the person mentioned a deadline, compare it with the delivery estimate and tell them plainly when the estimate falls after it. Example: {"pages":1,"service":"certified"}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "quote_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoPage count from 1 to 10. Provide exactly one of pages or pdf_base64; omit pages when providing a PDF.
serviceYes
pdf_base64NoA base64-encoded PDF whose pages we count for the quote. Provide exactly one of pages or pdf_base64; omit pages when providing a PDF. Neither field takes precedence: sending both is rejected, even if the counts agree.

Output Schema

NameRequiredDescriptionDefault
pagesYes
serviceYes
currencyYes
line_itemsYes
total_centsYes
partner_cost_centsYesPublic printing-and-postage cost in USD cents. The itemized price adds a 10% service fee; total_cents is before any Stripe sales tax.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, and the description still adds real value: quoting is free, unknown fields yield invalid_request with error.fix naming each rejected field, and the no-refund/no-delivery-guarantee policy is disclosed. The extra material about refunds and deadlines sits outside the quote operation itself, so it is useful context rather than pure tool behavior.

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?

Purpose and pricing are front-loaded, but the paragraph drifts into refund policy and deadline-comparison coaching that is tangential to obtaining a quote. The example is helpful, yet a few sentences could be trimmed without losing selection-relevant 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?

With an output schema present, return values need not be explained, and the description still covers pricing, error semantics for unknown fields, input exclusivity, and a concrete example. An agent has everything needed to call this correctly on the first attempt.

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 67% and the schema already explains the pages/pdf_base64 exclusivity. The description adds meaning the schema lacks: certified_err means an electronic Return Receipt, and per-page pricing ($9.04 vs $12.24) explains why page count matters. The worked example reinforces the required service field.

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?

Opens with a specific verb and resource: "Get an itemized price for 1-10 pages or count a base64 PDF." The scope (1-10 pages) and the two input modes are stated up front, and "Quoting never creates, pays for or mails a letter" implicitly separates it from create_letter and send_letter_now.

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?

Clear guidance on selecting the service variant ("For a return receipt, use service certified_err") and on when exact page counts matter ("use quote_letter for the exact page count"). It gives solid context but never explicitly rules out sibling tools such as get_letter for an existing letter's status.

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