Argorant

Check inbox orders

argorant_inbox_order_status

Read-onlyIdempotent

Show the workspace's mailbox orders, or one order with order_id, with each order's step (awaiting_payment, setting_up, aging, ready or attention), how it was ordered and paid, every domain with its expiry date, yearly renewal price and renewal state, how many mailboxes are created, when aging ends, and the billing bundles with their bundle_id and cancel reasons. Use it to follow an order from argorant_order_inboxes and to get the ids for argorant_set_inbox_domain_renewal, argorant_cancel_inbox_bundle or argorant_set_order_tags. New mailboxes wait 24 hours after setup before they send. More in the docs at https://docs.argorant.com/docs/agents/tools#new-inboxes

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": "argorant_inbox_order_status"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	No	One order's id. Leave it out for every order.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/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, so the safety profile is covered. The description adds genuine behavioral context beyond them: the order lifecycle states (awaiting_payment, setting_up, aging, ready, attention), when aging ends, and the operational constraint that new mailboxes wait 24 hours after setup before sending. It does not mention result volume or pagination for the all-orders mode.

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

Conciseness3/5

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

The purpose is front-loaded and the routing sentence is high value, but the long enumeration of every returned field (domain expiry, renewal price, mailbox counts, bundle cancel reasons) largely duplicates the output schema and makes the opening sentence unwieldy. The trailing docs link is useful but the field list could be trimmed.

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 single-optional-parameter read tool with annotations and an output schema, the description covers purpose, routing, id handoff to sibling mutations, and lifecycle timing. The only meaningful omission is any indication of result size or pagination when listing all orders.

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 schema already documents order_id as "One order's id. Leave it out for every order." The description restates the same semantics without adding format, id-source or error behavior. Baseline 3 applies when the schema carries the parameter meaning.

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?

States a specific verb and resource ("Show the workspace's mailbox orders, or one order with order_id") and enumerates the exact returned fields including order step values. It is clearly distinguishable from argorant_order_inboxes (which places orders) and argorant_list_inboxes (which lists mailboxes).

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

Usage Guidelines5/5

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

Explicitly routes the agent: use it to follow an order created by argorant_order_inboxes, and to obtain the ids needed by argorant_set_inbox_domain_renewal, argorant_cancel_inbox_bundle and argorant_set_order_tags. The conditional for the single-order mode ("or one order with order_id") is also stated.

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

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