PostalForm

Get order status

postalform.get_order_status

Read-onlyIdempotent

Read payment status and total, processing, stored mailing/carrier status, the latest 50 public tracking events, and electronic return receipt availability. Use payment_status_label and payment_status_description: payment_authorized means authorized awaiting capture, even when is_paid=false and paid_at=null. Do not request another payment for authorized, processing or received payments. Bulk orders also return campaign_url, recipient count and per-status counts; use the campaign dashboard for individual recipients. Missing carrier evidence is null; processing or a tracking number alone does not prove mailing or delivery. This read does not pay, mail, or acquire receipts.

Input Schema

Name	Required	Description	Default
`order_id`	Yes	PostalForm order id.

Output Schema

Name	Required	Description	Default
`bulk`	No
`view`	Yes
`error`	No
`found`	Yes
`carrier`	No
`is_paid`	No
`paid_at`	No
`currency`	No
`order_id`	Yes
`price_usd`	No
`signed_by`	No
`page_count`	No
`status_url`	No
`next_action`	No
`campaign_url`	No
`checkout_url`	No
`current_step`	No
`mailing_status`	No
`payment_status`	No
`delivery_status`	No
`payment_options`	No
`tracking_events`	No
`tracking_number`	No
`tracking_updated_at`	No
`payment_status_label`	No
`estimated_delivery_at`	No
`delivery_status_detail`	No
`electronic_return_receipt`	No
`mailing_status_normalized`	No
`payment_status_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 5, 2026

addedOutput schema / properties / currency

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / paid_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / payment_status_description
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / payment_status_label
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / price_usd

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial context on top: the 50-event cap on tracking history, null semantics for missing carrier evidence, the warning that a tracking number alone does not prove mailing or delivery, and the extra bulk-order fields (campaign_url, recipient count, per-status counts). This is exactly the kind of behavior-not-visible-in-schema disclosure that matters.

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?

Information is front-loaded with the return contents first, then interpretation rules, then exclusions, and nearly every clause earns its place. It is dense and packs many distinct claims into a few sentences, which borders on overload but remains scannable.

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?

A read-only, single-parameter tool with an output schema and full annotation coverage; the description nonetheless covers the interpretive traps (authorized vs paid, null carrier evidence) that an agent would otherwise get wrong. Nothing needed to invoke or interpret the result appears to be missing.

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 100% for the single order_id parameter (documented as 'PostalForm order id.' with a UUID pattern), so the schema carries the parameter burden. The description never mentions order_id or adds format expectations beyond it, making the baseline 3 the correct score.

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?

Names a specific verb ('Read') and enumerates exactly which parts of an order are returned: payment status and total, processing, stored mailing/carrier status, the latest 50 tracking events, and return receipt availability. It also explicitly contrasts with sibling mutations ('This read does not pay, mail, or acquire receipts'), so an agent can separate it from pay_order and the create_* tools without opening a 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 real decision guidance: authorized means awaiting capture even when is_paid=false, and 'Do not request another payment for authorized, processing or received payments' sets an explicit when-not for a follow-up action. It also redirects recipient-level lookups to the campaign dashboard. It stops short of an explicit 'call this before pay_order' statement, so selection is strong but not fully stated.

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

All PostalForm 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.

Resources

Need Help?