Handsome Hosting

Buy a domain

buy_domain

Destructive

Mint an approval for the person to buy an available domain for a year, optionally attached to a running service. Mails the link and returns actionId and approveUrl; the click opens the website buy page prefilled with the name and the service, where the person enters the registrant details and pays. Nothing is registered or charged here; the approval reads done once paid.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	the full name, for example shop.com
`serviceId`	No	the running service to attach the name to; omit to buy it on its own

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark this as a write and destructive operation, but the description adds material detail: it only mints an approval, emails a link, returns actionId and approveUrl, does not register or charge here, and completes after external payment. This gives an agent the exact side-effect and completion model it needs.

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 core action is front-loaded, followed by the approval flow and the no-charge caveat. Every sentence carries operational value with no repetition or filler.

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

Completeness4/5

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

With an output schema present, the description need not document return fields, and it covers both parameters plus the external completion flow. The main omission is explicit prerequisite/routing guidance for checking availability or handling existing domains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds that name is a full domain, serviceId is an optional running service, and the purchase is for a year. It does not add schema syntax, but it gives useful semantic context beyond the parameter descriptions.

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 gives a precise verb and object: it mints an approval to buy an available domain for one year, optionally tied to a running service. This is clearly distinguishable from search, status, and attach/connect siblings even though none are named explicitly.

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 use case is clear—buying an available domain—and it notes the optional service attachment. However, it does not explicitly say to check availability with search_domain first or when to prefer attach_domain/connect_domain for existing domains, so usage is implied rather than fully routed.

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

All Handsome Hosting tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?