Skip to main content
Glama

dynadot_set_transfer_auth_code

Submit or update the transfer authorization code on a domain order to enable or correct a domain transfer.

Instructions

Submit or update the transfer authorization code on an 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>",
      "authCode": "<authCode>"
    },
    "name": "dynadot_set_transfer_auth_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdNo
authCodeYes
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.5/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, yet it only implies mutation via 'submit or update'. It does not say whether an existing code is overwritten, what permissions or order state are required, or what happens on failure. The phrase 'on an order' also sits awkwardly with a schema where orderId is optional and domainName is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short and front-loaded, but here brevity works against the definition: it omits required context rather than trimming redundancy. There is no wasted wording, yet the sentence is under-specified for a three-parameter mutation tool.

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?

With no annotations, no output schema, and 0% schema description coverage on a mutation tool, the definition should explain parameters, preconditions, and effects. It supplies none of these, leaving the agent to guess how to address the order and what the call changes.

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 0%, so the description must compensate and it largely does not. It hints at authCode and an order, but never explains domainName (a required parameter), nor clarifies how domainName and the optional orderId relate as identifiers.

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 names a specific verb pair ('submit or update') and a specific resource ('the transfer authorization code on an order'), which is clearly distinct from read-side siblings like dynadot_get_transfer_auth_code. It stops short of explicitly naming that sibling, but the write intent is unambiguous.

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 rather than dynadot_get_transfer_auth_code or dynadot_transfer_in, nor any stated prerequisites (e.g. an existing transfer order, ownership of the domain). The only implied usage is that a code exists to be set.

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