Skip to main content
Glama

Sendpaper

by io.github.ryan-tish
OverviewDiscussionsAdmin

Create a letter

create_letter

Create a printed letter order (up to 3 pages, 8.5x11, mailed in a #10 envelope) and get a payment link. Mails only after the user pays. Set certified to "certified" ($14.99) for USPS Certified Mail with tracking and proof of delivery, or "certified_return_receipt" ($19.99) to add the recipient's signature; use these when the user needs proof (landlord notices, legal or tax replies, disputes). Regular letters are $4.99.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
fromYesReturn address; printed on the mail piece
contentYes
certifiedNoUSPS Certified Mail. "certified" ($14.99): tracking number and proof of mailing and delivery. "certified_return_receipt" ($19.99): adds the recipient's signature as proof of delivery, which landlords, courts and agencies often require. "none" ($4.99): regular First-Class.none
customer_emailNoWhere to send the receipt and status updates
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / certified
      Added value: +{
+  "default": "none",
+  "description": "USPS Certified Mail. \"certified\" ($14.99): tracking number and proof of mailing and delivery. \"certified_return_receipt\" ($19.99): adds the recipient's signature as proof of delivery, which landlords, courts and agencies often require. \"none\" ($4.99): regular First-Class.",
+  "enum": [
+    "none",
+    "certified",
+    "certified_return_receipt"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely useful lifecycle context beyond them: the order is not mailed until the user pays, and a payment link is returned. It stops short of explaining idempotency behavior, retry semantics, or what happens if payment never completes.

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?

Three sentences, front-loaded with the core action and output, then the certification options. The price details in the second sentence are dense but each element maps to a real decision the agent must make, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully names the return value (payment link). It covers the highest-stakes decision (certified level) well, but for a mutation tool with nested objects and six parameters it never addresses idempotency_key or customer_email semantics, which is a real gap.

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 50%. The description thoroughly explains the certified enum and its prices, duplicating and enriching the schema's own enum description, and implies the content/page limit. It adds nothing for customer_email, idempotency_key, font, or the nested to/from address objects, leaving several parameters documented only (or not at all) in the schema.

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 and resource ('Create a printed letter order') plus concrete physical scope (up to 3 pages, 8.5x11, #10 envelope) and the immediate outcome (payment link). An agent can distinguish this from create_postcard or pay_order without opening the schema.

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?

Gives clear situational guidance for the certified tiers with named use cases (landlord notices, legal or tax replies, disputes) and the price trade-off against regular mail. It does not, however, say when to choose this tool over sibling create_postcard or how it relates to the pay_order/cancel_order lifecycle.

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

All Sendpaper toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources