Skip to main content
Glama

dynadot_cancel_transfer

Cancel a pending domain transfer order by specifying the domain name and optional order ID, so you can stop an unwanted transfer before it completes.

Instructions

Cancel a pending transfer order.

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": {
      "domainName": "<domainName>"
    },
    "name": "dynadot_cancel_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdNo
domainNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / orderId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / orderId / type
      Added value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv2.0.1

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It signals that this is a mutation and applies only to pending transfers, but it does not say whether cancellation is irreversible, what happens to the order afterward, required permissions, or any side effects.

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 description is a single front-loaded sentence with no wasted wording. It is structurally clean, though its brevity is a completeness issue rather than a conciseness problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with two parameters, zero schema description coverage, no annotations, and no output schema, the definition is far too sparse. It identifies the core action but omits critical context needed to invoke it correctly and understand its effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention either parameter. It gives no meaning for orderId or domainName, does not explain that domainName is required and orderId is optional, and does not clarify the relationship between them.

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?

The description states a specific verb and resource: "Cancel a pending transfer order." This clearly indicates a cancellation operation on a transfer order and implicitly distinguishes it from read-only siblings like get_transfer_status, but it does not explicitly name or differentiate alternatives.

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

Usage Guidelines2/5

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

The only usage guidance is the word "pending," which implies a precondition but does not explain when to use this tool versus alternatives such as get_transfer_status. There are no exclusions, prerequisites, or alternative routes mentioned.

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

Deploy Server

Other Tools