Argorant

Cancel a bundle of mailboxes

argorant_cancel_inbox_bundle

Destructive

Cancel one bundle of ordered mailboxes. Billing for them stops now, with no refund; they keep working until the paid period ends and are then deleted for good. Their domains stop renewing too, unless keep_domains=true. Use it to end a bundle; to stop only a domain's renewal use argorant_set_inbox_domain_renewal, and to stop using one mailbox use argorant_update_inbox or argorant_disconnect_inbox. Ask the user for explicit approval first, and ask why. Only the workspace owner can cancel. Sending it again returns the first cancellation. More in the docs at https://docs.argorant.com/docs/agents/tools#new-inboxes

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>",
      "bundle_id": "<bundle_id>",
      "reason": "<reason>"
    },
    "name": "argorant_cancel_inbox_bundle"
  }
}

Input Schema

Name	Required	Description
`note`	No	Optional words from the user
`reason`	Yes	Why the user cancels, one of too_expensive, not_sending_enough, deliverability, switching_provider, campaign_finished or other.
`order_id`	Yes	The order's id, from argorant_inbox_order_status.
`bundle_id`	Yes	The bundle's id, from argorant_inbox_order_status.
`keep_domains`	No	true keeps the domains renewing after the mailboxes end. Off by default.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond that: billing stops immediately with no refund, mailboxes keep working until the paid period ends then are permanently deleted, domains stop renewing unless keep_domains=true, and re-sending is idempotent (returns the first cancellation). These are exactly the consequences an agent needs before invoking a destructive tool.

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?

Front-loads the action and its irreversible consequence, then alternatives, then approval and permission requirements, then idempotency. Dense but every sentence carries distinct, decision-relevant information with no filler.

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 destructive, owner-restricted, idempotent cancellation tool, the description covers consequences, alternatives, prerequisites, and repeat-call behavior; an output schema exists so return values need not be explained. Nothing material is missing.

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 100%, so the baseline is 3; the description adds real meaning by explaining the downstream effect of keep_domains (domains keep renewing) and by tying reason to the user-approval flow. It does not add format or sourcing detail for order_id/bundle_id, but the schema already covers those.

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 ('Cancel one bundle of ordered mailboxes') and immediately distinguishes it from the three sibling tools that handle narrower cases (domain renewal, single mailbox update, disconnect). An agent can route correctly without opening any schema.

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?

Gives explicit when-to-use plus named alternatives with their distinct conditions: argorant_set_inbox_domain_renewal for renewal-only, argorant_update_inbox / argorant_disconnect_inbox for a single mailbox. It also adds a procedural prerequisite (ask the user for explicit approval and ask why) and an authorization constraint (workspace owner only).

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.