Skip to main content
Glama

set_whois_contacts

Update WHOIS contact information for a domain by specifying contact IDs for registrant, admin, technical, and billing contacts.

Instructions

Set WHOIS contact information for a domain. Specify contact IDs for registrant, admin, technical, and/or billing contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to update
registrant_contactNoContact ID for the registrant
admin_contactNoContact ID for the admin contact
technical_contactNoContact ID for the technical contact
billing_contactNoContact ID for the billing contact

Implementation Reference

  • The MCP tool registration and handler for 'set_whois_contacts', which collects contact IDs and calls the Dynadot client.
    server.tool(
      "set_whois_contacts",
      "Set WHOIS contact information for a domain. Specify contact IDs for " +
        "registrant, admin, technical, and/or billing contacts.",
      {
        domain: z.string().describe("Domain name to update"),
        registrant_contact: z
          .string()
          .optional()
          .describe("Contact ID for the registrant"),
        admin_contact: z
          .string()
          .optional()
          .describe("Contact ID for the admin contact"),
        technical_contact: z
          .string()
          .optional()
          .describe("Contact ID for the technical contact"),
        billing_contact: z
          .string()
          .optional()
          .describe("Contact ID for the billing contact"),
      },
      async ({ domain, registrant_contact, admin_contact, technical_contact, billing_contact }) => {
        try {
          const contacts: Record<string, string> = {};
          if (registrant_contact) contacts.registrant_contact = registrant_contact;
          if (admin_contact) contacts.admin_contact = admin_contact;
          if (technical_contact) contacts.technical_contact = technical_contact;
          if (billing_contact) contacts.billing_contact = billing_contact;
          const result = await client.setWhoisContacts(domain, contacts);
          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 set WHOIS contacts: ${msg}` },
            ],
            isError: true,
          };
        }
      }
    );
  • The actual Dynadot API client implementation for setting WHOIS contacts, mapping to the 'set_whois' command.
    async setWhoisContacts(domain: string, contacts: Record<string, string>): Promise<DynadotResponse> {
      return this.call("set_whois", { domain, ...contacts });
    }
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 implies a mutation operation ('Set') but lacks details on permissions required, whether changes are reversible, error handling (e.g., invalid contact IDs), or side effects. This is inadequate for a tool that modifies domain WHOIS data.

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?

The description is a single, efficient sentence with zero wasted words. It front-loads the core purpose and succinctly specifies the contact types, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like authentication needs, rate limits, or response format, leaving significant gaps for an AI agent to understand how to invoke it safely and interpret results.

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%, so the schema fully documents all parameters. The description adds minimal value by listing the contact types (registrant, admin, technical, billing) but doesn't provide additional context beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate given the comprehensive schema.

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 clearly states the action ('Set WHOIS contact information') and resource ('for a domain'), specifying the types of contacts that can be updated. It distinguishes itself from sibling tools like 'edit_contact' or 'set_contact_regional_setting' by focusing on domain WHOIS contacts rather than general contact editing or regional settings.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing contact IDs from 'list_contacts'), exclusions, or comparisons to similar tools like 'edit_contact' for general contact modifications or 'set_contact_regional_setting' for regional updates.

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