Sendpaper

Get prices

get_pricing

Read-only

List mail products and prices (USD, printing + USPS First-Class postage included, US addresses only).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`express`	Yes	Surcharge for express delivery
`payment`	Yes
`products`	Yes
`pdf_letters`	Yes	Mailing your own PDF as a letter
`letter_photo`	Yes	Surcharge for a letter printed in color (a photo, or a PDF with color on)
`first_order_discount`	Yes	Current first-order discount (0 when none)

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 8, 2026

addedOutput schema / properties / express

Added value: +{
+  "additionalProperties": false,
+  "description": "Surcharge for express delivery",
+  "properties": {
+    "amount_cents": {
+      "type": "number"
+    },
+    "description": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "amount_cents",
+    "description"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / first_order_discount / description
```
Added value: +"Current first-order discount (0 when none)"
```
removedOutput schema / properties / first_order_discount / properties / amount_cents
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / first_order_discount / properties / percent
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / first_order_discount / required

Previous value: -[
-  "amount_cents",
-  "description"
-]New value: +[
+  "percent",
+  "description"
+]

changedOutput schema / properties / letter_photo / description

Previous value: -"Surcharge for a letter with a photo (prints in color)"New value: +"Surcharge for a letter printed in color (a photo, or a PDF with color on)"

addedOutput schema / properties / pdf_letters

Added value: +{
+  "additionalProperties": false,
+  "description": "Mailing your own PDF as a letter",
+  "properties": {
+    "description": {
+      "type": "string"
+    },
+    "max_pages": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "max_pages",
+    "description"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "products",
-  "payment",
-  "first_order_discount",
-  "letter_photo"
-]New value: +[
+  "products",
+  "payment",
+  "first_order_discount",
+  "letter_photo",
+  "express",
+  "pdf_letters"
+]

Changed4 schema fields changedOct 5, 2026

addedOutput schema / properties / first_order_discount

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "amount_cents": {
+      "type": "number"
+    },
+    "description": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "amount_cents",
+    "description"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / first_postcard_free

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "available": {
-      "type": "boolean"
-    },
-    "description": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "description",
-    "available"
-  ],
-  "type": "object"
-}

addedOutput schema / properties / letter_photo

Added value: +{
+  "additionalProperties": false,
+  "description": "Surcharge for a letter with a photo (prints in color)",
+  "properties": {
+    "amount_cents": {
+      "type": "number"
+    },
+    "description": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "amount_cents",
+    "description"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "products",
-  "payment",
-  "first_postcard_free"
-]New value: +[
+  "products",
+  "payment",
+  "first_order_discount",
+  "letter_photo"
+]

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "first_postcard_free": {
+      "additionalProperties": false,
+      "properties": {
+        "available": {
+          "type": "boolean"
+        },
+        "description": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "description",
+        "available"
+      ],
+      "type": "object"
+    },
+    "payment": {
+      "additionalProperties": {},
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "options": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "stripe_network_id": {
+          "description": "Scope Stripe shared payment tokens to this network id",
+          "type": "string"
+        }
+      },
+      "required": [
+        "options",
+        "currency"
+      ],
+      "type": "object"
+    },
+    "products": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cents": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "description": "Display price, e.g. $2.99",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "cents",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "products",
+    "payment",
+    "first_postcard_free"
+  ],
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds meaningful business context beyond that: prices are in USD, include printing plus USPS First-Class postage, and apply to US addresses only — constraints an agent cannot derive from annotations or schema.

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

Conciseness5/5

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

A single front-loaded sentence that conveys the resource and three scoping constraints with no filler. Every clause earns its place.

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 no parameters, full annotation coverage, and an output schema handling return values, the description only needs to convey scope — which it does (USD, postage included, US-only). Nothing an agent needs to call this 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?

The tool takes zero parameters, so the baseline is 4. Schema coverage is 100% and there is nothing for the description to disambiguate about inputs.

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?

States a specific verb (List) and resource (mail products and prices) with currency and scope qualifiers, so the agent immediately knows this is a catalog lookup rather than an ordering action. It does not name sibling tools, but the contrast with create_letter/create_postcard/pay_order is obvious from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use is implied (fetch price list, presumably before creating or paying for an order) but never stated. There are no explicit when/when-not cues or references to alternatives, so the agent must infer the trigger from context.

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

All Sendpaper tools Inspect

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.