Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Stop a domain's renewal (old name)

argorant_cancel_inbox_domain
Destructive

The old name for argorant_set_inbox_domain_renewal with on=false. Use it only from older clients and use that tool instead. It stops renewal for one ordered domain, which keeps working until its expiry date and is then not renewed or charged again. Nothing is charged now and domains are never deleted early. Ask the user for explicit approval first. Only the workspace owner can change it. 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>"
    },
    "name": "argorant_cancel_inbox_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe ordered domain to stop renewing.
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.5/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and readOnlyHint=false; the description adds the far more useful nuance that nothing is charged now, the domain keeps working until expiry, and nothing is deleted early, tempering the 'destructive' signal. It also discloses the owner-only authorization requirement and the explicit-approval workflow, which annotations cannot convey.

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 legacy-alias fact and the replacement tool are front-loaded, followed by effect, billing, approval, and permission details with little waste. The trailing docs link uses the anchor '#new-inboxes', which does not match domain-renewal content and slightly undercuts an otherwise tight structure.

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 two-parameter mutation with full annotations and an output schema, the description covers effect, reversibility implications, billing, authorization, and approval requirements, leaving little an agent needs unstated. The only shortfall is the mismatched documentation link, which is unlikely to guide behavior correctly.

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 domain as the ordered domain to stop renewing and order_id as coming from argorant_inbox_order_status. The description restates the single-domain scope but adds no format, lookup, or edge-case detail beyond the schema, so baseline 3 is appropriate.

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 states a specific effect (stops renewal for one ordered domain) and explicitly frames the tool as the legacy alias for argorant_set_inbox_domain_renewal with on=false, which is named in the sibling list. An agent can tell exactly what it does and which tool supersedes it without opening 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?

It gives an explicit routing rule: use only from older clients, otherwise use argorant_set_inbox_domain_renewal. It also adds a gating prerequisite (ask the user for explicit approval first) and a permission constraint (workspace owner only), so when-to-use and when-not-to-use are both stated.

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