Card Mailer

Mailing status

get_mailing_status

Read-onlyIdempotent

Returns a Card Mailer order's payment, printing, mailing or delivery status, send date, estimated arrival and per-recipient counts. The mailing_id is the last part of the order link. Does not change the order or track other USPS mail.

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": {
      "mailing_id": "<mailing_id>"
    },
    "name": "get_mailing_status"
  }
}

Input Schema

Name	Required	Description	Default
`mailing_id`	Yes

Output Schema

Name	Required	Description	Default
`kind`	Yes
`total`	Yes
`counts`	Yes
`status`	Yes
`quantity`	Yes
`send_date`	Yes
`mailing_id`	Yes
`checkout_url`	Yes
`arrives_between`	Yes
`addresses_deleted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value on top by stating the read-only scope in plain language and by scoping which mailings it does or does not report on, though it says nothing about error or not-found behavior.

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?

Two sentences, front-loaded with the resource and returned fields, followed by a tight exclusion clause. There is no filler and every clause adds either scope or constraint information.

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?

For a one-parameter read tool with full annotation coverage and an output schema that documents the response shape, nothing an agent needs in order to invoke it correctly is missing: identity, what comes back at a high level, and the id's origin are all stated.

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?

With 0% schema description coverage, the description carries the full burden for the single parameter, and it delivers exactly the operationally useful fact: 'The mailing_id is the last part of the order link.' That is a real derivation instruction an agent could not infer from the bare string schema, though it does not state what a malformed or unknown id does.

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?

The description opens with a specific verb and resource ('Returns a Card Mailer order's payment, printing, mailing or delivery status') and enumerates the concrete return fields (send date, estimated arrival, per-recipient counts). It also explicitly bounds itself against sibling workflows by noting it does not track other USPS mail, so an agent can separate it from order-creation or quoting tools.

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?

It gives clear when-not guidance ('Does not change the order or track other USPS mail'), which steers agents away from using it for mutations or general USPS tracking. It stops short of naming an alternative tool for those cases, so it is strong context rather than a full use/avoid routing map.

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

All Card Mailer 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?