Skip to main content
Glama

dynadot_authorize_transfer_away

Approve or deny a domain transfer away by specifying the domain name, order ID, and authorization decision.

Instructions

Approve or deny an outgoing transfer.

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>",
      "orderId": "<orderId>",
      "authorize": "<authorize>"
    },
    "name": "dynadot_authorize_transfer_away"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
authorizeYestrue to approve, false to deny
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.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says approve or deny but does not disclose consequences, reversibility, required permissions, or what happens to the transfer after approval or denial.

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?

A single short sentence with no filler, and the action is front-loaded. It is appropriately sized for a tool whose details should be in the schema and annotations.

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 three-required-parameter mutation tool with no annotations and no output schema, the definition is too sparse. It should explain transfer effects, required identifiers, and consequences of approval or denial.

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

Parameters2/5

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

Schema description coverage is only 33%, with just 'authorize' documented as true/false in the schema. The description does not explain domainName or orderId, and adds no meaning beyond the schema's boolean hint.

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 action ('Approve or deny') and resource ('an outgoing transfer'), which is clearer than a generic transfer tool. It does not explicitly differentiate itself from siblings such as cancel_transfer or get_transfer_status, so it stops short of 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 Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like cancel_transfer or get_transfer_status, and no prerequisites or workflow context are given. The agent must infer usage from the name and one-line description.

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