Skip to main content
Glama

Withdraw domain cancellation

uncancel_domain
Idempotent

Reactivate a cancelled domain subscription before it expires. Creates a new billing subscription, re-enables auto-renew at the registrar, and clears the cancellation.

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>"
    },
    "name": "uncancel_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say not-read-only, idempotent, non-destructive; the description adds the material facts an agent needs — that this creates a NEW billing subscription (a charge is incurred), re-enables auto-renew at the registrar, and clears the cancellation. Those are non-obvious side effects beyond the annotation set, and the timing constraint ('before it expires') flags the failure boundary.

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?

Two sentences, no waste, with the core action front-loaded and the side effects following as supporting detail. Every clause ('before it expires', billing, auto-renew, cancellation) contributes information an agent would otherwise have to guess.

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 single-parameter tool with no output schema and safety already covered by annotations, the description supplies the consequential behavior (new billing subscription) that matters most. It leaves open the error path for an already-expired domain, which is the main remaining gap.

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?

There is exactly one parameter and schema coverage is 100%, with the schema itself documenting 'id' and enforcing a 24-hex-character pattern. The description adds nothing about the identifier, so the baseline of 3 applies — the schema carries this dimension entirely.

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+resource pair ('Reactivate a cancelled domain subscription') that is unambiguously the inverse of the sibling cancel_domain, and the three enumerated side effects pin down what reactivation actually means. It stops just short of explicitly naming a sibling to prefer under some condition, which keeps it from a 5.

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

Usage Guidelines4/5

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

The phrase 'before it expires' gives a clear eligibility window and implicitly tells the agent this is the undo path for cancel_domain. It offers no explicit exclusions (e.g. what to do if the domain already expired, or whether a fresh register_domain is then the alternative), so guidance is contextual rather than complete.

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.