Letter IRL

Check an order's status

get_order_status

Read-only

Retrieve the latest status timeline for a letter or postcard order. If no orderId is provided, returns the most recent order. Delivery is an estimate from the printing partner's schedule.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_order_status"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	No

Output Schema

Name	Required	Description
`mailOn`	No	Sent with an arrival date: the day it goes to the printer, YYYY-MM-DD
`orderId`	Yes
`arriveBy`	No	Sent with an arrival date: the date it aims to arrive by, YYYY-MM-DD
`cancellable`	No	With an arrival date: whether it can still be cancelled free, before it goes to the printer
`mailService`	No	Present only for USPS Certified Mail: certified, or certified_return_receipt (with an electronic return receipt).
`certifiedNote`	No	Certified mail only: what to tell the person about the tracking number and the return receipt. It promises nothing about delivery or legal effect.
`currentStatus`	Yes	The order's status. delivered means the printer's estimated delivery date has passed; no carrier confirmed it, so say its delivery is estimated, not that it was delivered
`statusTimeline`	Yes
`canSendFollowUp`	No
`trackingSupport`	No	How the order can be tracked. estimated_only: the status comes from the printer, and delivery is estimated, not confirmed by a carrier. carrier_tracking: USPS's own tracking number is stored for a letter that went out (certified mail), so USPS's page shows the scans; this status is still the printer's.
`recipientSummary`	Yes
`carrierTrackingUrl`	No	Certified mail only, with the tracking number: the USPS page that shows where the piece is.
`carrierTrackingNumber`	No	Certified mail only: USPS's tracking number, once the printer has set it and Letter IRL's status sync has stored it. It is not the order id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds behavior beyond that: the no-argument default of returning the latest order, the fact that the response is a timeline of statuses, and the caveat that delivery dates are estimates from the printing partner rather than guarantees. That caveat is exactly the kind of interpretive context annotations cannot carry.

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?

Two short sentences with the core purpose front-loaded, followed by a compact caveat. Every sentence carries information; the only mild slack is that the delivery-estimate note is separated from the timeline statement rather than integrated.

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 an output schema present, return-value detail is not needed, and annotations cover safety. The description supplies the missing pieces for a one-optional-param read tool: purpose, default behavior, and a caveat about interpreting estimated delivery. Only the orderId format and explicit sibling routing remain unaddressed.

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 0% and the single orderId property has no type description or format guidance in the schema, so the description carries the burden. It does explain that orderId is optional and what happens when it is absent, which is the key semantic fact; it does not describe the expected ID format or where an agent obtains one.

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 ('Retrieve the latest status timeline for a letter or postcard order'), which separates it from siblings like get_purchase_status and get_draft_status by naming the order object. It stops short of explicitly naming those siblings, so an agent still has to infer the boundary, but the resource scope is clear.

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 description gives one concrete usage rule — omitting orderId returns the most recent order — which is genuinely helpful for calling the tool. It offers no when-to-use vs. when-not guidance relative to the status-related siblings, so selection among them is left to inference.

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

All Letter IRL 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?