Skip to main content
Glama

authorize_transfer_away

Authorize the transfer of a domain to another registrar by specifying the domain name. This action approves the outgoing transfer request.

Instructions

Approve an outgoing domain transfer to another registrar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to authorize for transfer away

Implementation Reference

  • The MCP tool handler for 'authorize_transfer_away'. It defines the tool schema (domain string input), description, and async handler that calls client.authorizeTransferAway() and returns the JSON result.
    // ─── authorize_transfer_away ──────────────────────────────────
    
    server.tool(
      "authorize_transfer_away",
      "Approve an outgoing domain transfer to another registrar.",
      {
        domain: z.string().describe("Domain name to authorize for transfer away"),
      },
      async ({ domain }) => {
        try {
          const result = await client.authorizeTransferAway(domain);
          return {
            content: [
              { type: "text" as const, text: JSON.stringify(result, null, 2) },
            ],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return {
            content: [
              { type: "text" as const, text: `Failed to authorize transfer: ${msg}` },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema for the tool input: 'domain' string describing the domain name to authorize for transfer away.
    {
      domain: z.string().describe("Domain name to authorize for transfer away"),
    },
  • The tool is registered via server.tool('authorize_transfer_away', ...) inside registerTransferTools(), which is called from src/index.ts with the McpServer and DynadotClient instances.
    // ─── authorize_transfer_away ──────────────────────────────────
    
    server.tool(
      "authorize_transfer_away",
      "Approve an outgoing domain transfer to another registrar.",
      {
        domain: z.string().describe("Domain name to authorize for transfer away"),
      },
      async ({ domain }) => {
        try {
          const result = await client.authorizeTransferAway(domain);
          return {
            content: [
              { type: "text" as const, text: JSON.stringify(result, null, 2) },
            ],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return {
            content: [
              { type: "text" as const, text: `Failed to authorize transfer: ${msg}` },
            ],
            isError: true,
          };
        }
      }
    );
  • The DynadotClient.authorizeTransferAway() helper method that calls the Dynadot API3 'authorize_transfer_away' command with the domain parameter.
    async authorizeTransferAway(domain: string): Promise<DynadotResponse> {
      return this.call("authorize_transfer_away", { domain });
    }
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It merely states 'approve' without detailing consequences (e.g., irreversible action, required auth code, or impact on domain status). The description lacks necessary transparency for a mutation operation.

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 sentence of 8 words, front-loading the action and resource with zero waste. Every word earns its place.

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

Completeness3/5

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

For a simple tool with one required parameter and no output schema, the description is minimal. It explains the high-level purpose but lacks completeness on what the approval triggers (e.g., irreversible, need auth code). Adequate but could elaborate slightly.

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 description coverage is 100% with a single parameter 'domain' described as 'Domain name to authorize for transfer away'. The tool description adds no extra meaning beyond 'outgoing domain transfer', so baseline 3 applies.

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

Purpose5/5

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

The description 'Approve an outgoing domain transfer to another registrar' uses a specific verb ('approve') and resource ('outgoing domain transfer'), clearly differentiating from siblings like 'cancel_transfer' (cancel), 'get_transfer_status' (status check), and 'transfer_domain' (initiating transfer).

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 implies when to use (to approve a transfer) but provides no guidance on alternatives or exclusions. No mention of prerequisites like domain unlock or auth code availability, leaving the agent to infer context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/dynadot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server