@hofmeister/godaddy-mcp

get_registration_quote

Read-only

Get a domain registration price quote with no charge, locking the rate via a quote token and showing required ICANN agreements before you commit to registration.

Instructions

Get a price quote for registering a domain. This locks the price to a quoteToken for a short window and returns the required ICANN agreements that must be reviewed before registering. Read-only and does NOT charge the account. Step 1 of 2 of registration; step 2 is register_domain.

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": {
      "domain": "<domain>"
    },
    "name": "get_registration_quote"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to register, e.g. example.com (must be available).
`period`	No	Registration period in years (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Even though annotations provide readOnlyHint=true, the description adds meaningful behavioral details: it locks the price to a quoteToken for a short window, returns required ICANN agreements, and explicitly states it does not charge the account. This is valuable context beyond what the annotations already convey.

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 three sentences with no wasted words. It front-loads the core purpose, then explains the key side effect and workflow position, making it easy to parse quickly.

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

Completeness5/5

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

Despite having no output schema, the description indicates the key returned artifacts (quoteToken and ICANN agreements) and explains the locking behavior and no-charge guarantee. For a two-parameter, single-required-field tool, this is complete enough for an agent to invoke it correctly.

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 already documents both parameters (domain and period) adequately. The description adds minimal parameter-level meaning beyond the context of registering a domain, so a baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Get a price quote for registering a domain.' It clearly distinguishes itself from register_domain by explicitly identifying this as Step 1 of 2, so an agent can tell it apart from its closest sibling without opening the schema.

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

Usage Guidelines5/5

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

The description explicitly frames when to use the tool: as Step 1 of a two-step registration flow, with register_domain named as Step 2. It also clarifies that the tool is read-only and does not charge the account, which signals that it should be used before any actual registration mutation.

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

Deploy Server