Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Stop or turn back on a domain's renewal

argorant_set_inbox_domain_renewal
Destructive

Stop renewal (on=false) or turn renewal back on (on=true) for one ordered domain. Use it for a single domain; to cancel a whole bundle of mailboxes use argorant_cancel_inbox_bundle. Nothing is charged now either way. A stopped domain keeps working until its expiry date and is then not renewed, and domains are never deleted early. A domain with renewal on renews at its expiry date at its yearly renewal price, billed shortly before. Ask the user for explicit approval first. Only the workspace owner can change it. Tell the user the answer's message, which names the date and the price. 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>",
      "domain": "<domain>",
      "on": "<on>"
    },
    "name": "argorant_set_inbox_domain_renewal"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesfalse stops renewal, true turns renewal back on
domainYesThe ordered domain, from argorant_inbox_order_status.
order_idYesThe order's id, from argorant_inbox_order_status.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and readOnlyHint=false; the description goes well beyond by explaining that nothing is charged now, the stopped domain keeps working until expiry, domains are never deleted early, and renewal is billed at the yearly price shortly before expiry. It also discloses the owner-only auth requirement and instructs the agent to relay the response message containing date and price.

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?

The core action and its alternative are front-loaded in the first two sentences, and the billing/lifecycle facts each earn their place. There is minor redundancy in re-explaining the on boolean already documented in the schema, and the trailing docs URL is marginally useful 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 3-parameter mutation tool with full schema coverage and an output schema, the description supplies everything else an agent needs: lifecycle consequences, the absence of immediate charges, approval and permission requirements, and a note that the response message should be surfaced to the user.

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 coverage is 100% and already defines on as false=stop/true=resume and points order_id and domain at argorant_inbox_order_status, so the description's restatement of the boolean adds no new meaning. Baseline 3 applies since the schema carries all parameter semantics.

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?

Opens with a specific verb pair and resource: stop or re-enable renewal for a single ordered domain, with the boolean encoding stated inline. It also names the sibling it is not (argorant_cancel_inbox_bundle), so an agent can route correctly without reading either 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 scopes to one domain and routes bundle cancellation to argorant_cancel_inbox_bundle. It adds a precondition (ask the user for explicit approval first) and a permission constraint (workspace owner only), which is unusually complete when-to-use guidance.

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