Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Disconnect a mailbox

argorant_disconnect_inbox
DestructiveIdempotent

Disconnect one mailbox from Argorant. It is taken off every campaign and nothing more is sent from it; the mailbox and its emails are not deleted. Use it to stop using a mailbox for good; to pause it instead use argorant_update_inbox with active=false, and to take it off one campaign use argorant_remove_campaign_sender. Mailboxes ordered from Argorant keep being billed until they are cancelled with argorant_cancel_inbox_bundle. Ask the user for explicit approval first, and set confirmed=true only with that yes. It is free. More in the docs at https://docs.argorant.com/docs/agents/tools#mailboxes

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": {
      "email": "<email>"
    },
    "name": "argorant_disconnect_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe mailbox address to disconnect.
confirmedNotrue only after the user's explicit yes to disconnecting this mailbox

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the two things an agent would otherwise guess wrong: the mailbox and its emails are NOT deleted, and Argorant-ordered mailboxes keep being billed until cancelled separately. It also flags the operation as free and names the consent requirement, which is exactly the non-obvious behavioral context a destructive tool needs.

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-loaded with the definition and consequence, then the alternative-tool routing, then the billing caveat, then the consent rule, then the docs link. No sentence is filler — each carries a distinct decision-relevant fact despite the density.

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?

Output schema exists, so return values need not be explained, and the description covers consequences, alternatives, billing, cost, and consent. The only minor gap is stating whether the disconnect is reversible or how to reconnect the same address later.

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 both parameters are already documented. The description still adds procedural meaning to confirmed by tying it to a prior explicit user yes ("set confirmed=true only with that yes"), clarifying sequencing rather than just restating the field. The email parameter is not elaborated beyond the schema, which is acceptable at full coverage.

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?

"Disconnect one mailbox from Argorant" is a specific verb plus resource, and the very next clause defines the operational consequence: removed from every campaign, no further sends, mailbox and emails preserved. An agent can distinguish this from connect_smtp_mailbox or update_inbox 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?

Explicitly routes three alternatives: use argorant_update_inbox with active=false to pause, argorant_remove_campaign_sender to detach from a single campaign, and argorant_cancel_inbox_bundle to stop billing. It also states the precondition (ask the user for explicit approval first), which is a usage rule, not just a warning.

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

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