Skip to main content
Glama

Cancel domain

cancel_domain
Destructive

Cancel a domain subscription at the end of the current billing period. Disables auto-renew at the registrar. The domain stays active until the expiry date. This is a destructive operation. You MUST set confirm to true.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "cancel_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
confirmYesMust be true to confirm this operation

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is lower. The description still adds real behavioral context beyond the annotations: cancellation lands at the end of the billing period, auto-renew is disabled at the registrar, and the domain stays active until expiry — exactly the deferred-effect semantics an agent cannot see in structured fields.

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?

Four short sentences, front-loaded with the primary effect, then the mechanics, then the confirmation requirement. Slight redundancy in restating the confirm requirement that the schema already carries, but nothing is wasted overall.

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 destructive tool with annotations covering the safety profile, the description supplies the timing model and the confirm requirement that an agent needs to call it correctly. It stops short of stating reversibility (uncancel_domain exists) or whether the domain ID must be owned by the caller, but is otherwise sufficient.

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%, so both parameters are documented in the schema, including confirm's meaning. The description repeats the confirm requirement without adding syntax or format detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (cancel a domain subscription) plus the timing of the effect. It does not name the sibling that reverses it (uncancel_domain) or clarify against vps_cancel/webspace_cancel, so sibling differentiation is implied by the resource name rather than explicit.

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

Usage Guidelines3/5

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

The description conveys when the cancellation takes effect and that the operation must be confirmed, which implies usage. However, it offers no guidance on how this differs from uncancel_domain, whether cancellation can be reversed, or what prerequisites/authorization exist, so alternatives are left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.