Sendpaper

Check an order

get_order

Read-only

Get the status of a postcard or letter order by id (ord_...).

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": {
      "order_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	Order id, ord_…

Output Schema

Name	Required	Description
`id`	Yes	Order id, ord_…
`batch`	No	Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment.
`price`	Yes
`object`	Yes
`orders`	No	Every order in the group, when created with recipients
`status`	Yes	awaiting_payment, paid, printing, mailed, cancelled or refunded
`product`	Yes	Product id, e.g. postcard_4x6 or letter_certified
`discount`	Yes	First-order discount, already taken off price; null when none applies
`tracking`	Yes	USPS tracking, for Certified Mail once printed
`certified`	Yes	none, certified or certified_return_receipt
`order_url`	Yes	Order status page
`preview_url`	Yes	Exact print preview
`checkout_url`	Yes	Where the user pays; null once paid or cancelled
`product_name`	Yes
`status_detail`	Yes	Plain-English status to show the user
`preview_image_url`	No	PNG picture of the piece (postcard front and back, or the letter's first page) to show the user

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / preview_image_url

Added value: +{
+  "description": "PNG picture of the piece (postcard front and back, or the letter's first page) to show the user",
+  "type": "string"
+}

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / batch

Added value: +{
+  "additionalProperties": false,
+  "description": "Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment.",
+  "properties": {
+    "checkout_url": {
+      "description": "One payment link for every unpaid order in the group",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "description": "How many recipients (one order each)",
+      "type": "number"
+    },
+    "discount": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "amount_cents": {
+              "type": "number"
+            },
+            "display": {
+              "type": "string"
+            },
+            "reason": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "amount_cents",
+            "display",
+            "reason"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "price": {
+      "additionalProperties": false,
+      "description": "Total for the whole group",
+      "properties": {
+        "amount_cents": {
+          "type": "number"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "display": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount_cents",
+        "currency",
+        "display"
+      ],
+      "type": "object"
+    },
+    "url": {
+      "description": "Group page listing every recipient",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "count",
+    "url",
+    "checkout_url",
+    "price",
+    "discount"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / orders

Added value: +{
+  "description": "Every order in the group, when created with recipients",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "order_url": {
+        "type": "string"
+      },
+      "preview_url": {
+        "type": "string"
+      },
+      "to": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "to",
+      "order_url",
+      "preview_url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 5, 2026

addedOutput schema / properties / discount

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "amount_cents": {
+          "type": "number"
+        },
+        "display": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount_cents",
+        "display",
+        "reason"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "First-order discount, already taken off price; null when none applies"
+}

removedOutput schema / properties / first_postcard_free

Removed value: -{
-  "additionalProperties": false,
-  "description": "Present when the first-postcard-free offer applies",
-  "properties": {
-    "applied": {
-      "type": "boolean"
-    },
-    "eligible": {
-      "type": "boolean"
-    },
-    "how": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

changedOutput schema / required

Previous value: -[
-  "id",
-  "object",
-  "product",
-  "product_name",
-  "certified",
-  "status",
-  "status_detail",
-  "price",
-  "checkout_url",
-  "order_url",
-  "preview_url",
-  "tracking"
-]New value: +[
+  "id",
+  "object",
+  "product",
+  "product_name",
+  "certified",
+  "status",
+  "status_detail",
+  "price",
+  "checkout_url",
+  "order_url",
+  "preview_url",
+  "tracking",
+  "discount"
+]

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / order_id / description
```
Added value: +"Order id, ord_…"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "certified": {
+      "description": "none, certified or certified_return_receipt",
+      "type": "string"
+    },
+    "checkout_url": {
+      "description": "Where the user pays; null once paid or cancelled",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "first_postcard_free": {
+      "additionalProperties": false,
+      "description": "Present when the first-postcard-free offer applies",
+      "properties": {
+        "applied": {
+          "type": "boolean"
+        },
+        "eligible": {
+          "type": "boolean"
+        },
+        "how": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "id": {
+      "description": "Order id, ord_…",
+      "type": "string"
+    },
+    "object": {
+      "enum": [
+        "postcard",
+        "letter"
+      ],
+      "type": "string"
+    },
+    "order_url": {
+      "description": "Order status page",
+      "type": "string"
+    },
+    "preview_url": {
+      "description": "Exact print preview",
+      "type": "string"
+    },
+    "price": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_cents": {
+          "type": "number"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "display": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount_cents",
+        "currency",
+        "display"
+      ],
+      "type": "object"
+    },
+    "product": {
+      "description": "Product id, e.g. postcard_4x6 or letter_certified",
+      "type": "string"
+    },
+    "product_name": {
+      "type": "string"
+    },
+    "status": {
+      "description": "awaiting_payment, paid, printing, mailed, cancelled or refunded",
+      "type": "string"
+    },
+    "status_detail": {
+      "description": "Plain-English status to show the user",
+      "type": "string"
+    },
+    "tracking": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "number": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "number",
+            "url"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "USPS tracking, for Certified Mail once printed"
+    }
+  },
+  "required": [
+    "id",
+    "object",
+    "product",
+    "product_name",
+    "certified",
+    "status",
+    "status_detail",
+    "price",
+    "checkout_url",
+    "order_url",
+    "preview_url",
+    "tracking"
+  ],
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A3.6/5.0

Behavior3/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 the safety profile is covered without the description. The description adds the id prefix format hint, which is minor, and says nothing about ordering of results, caching, or error behavior for unknown ids.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Nothing could be removed without losing information.

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?

For a one-parameter read tool with full schema coverage, complete annotations, and an output schema that carries the return shape, the description is nearly sufficient. It only misses any note on error cases or what 'status' values may appear.

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 description coverage is 100% and the single parameter already documents 'Order id, ord_…'. The description's '(ord_...)' repeats what the schema provides rather than adding new meaning, so the baseline of 3 applies.

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 and resource ('Get the status of a postcard or letter order') and scopes it by id, so the agent can distinguish it from cancel_order or pay_order in practice. It never names a sibling explicitly, so it stops short of a 5.

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?

The read-only 'get the status' framing implies the usage context (lookup rather than mutation), but there is no explicit when-to-use, no prerequisites, and no mention of the alternative order-management tools. Implied usage only.

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.