Handsome Hosting

Attach a domain

attach_domain

Destructive

Point a domain bought here at a running, deployed service: the DNS zone is created or moved to the service address, the platform attaches the name and issues the certificate within about half an hour. Runs on the call, no approval: it costs nothing, and the same call moves the name to another service (the old one stops serving it). A name still registering is not-ready; a service with no deploy yet is not-deployed; a connected domain (one owned at another registrar) moves from the dashboard instead. The names are the account's heldDomains (unattached) and the domains of its services.

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>",
      "serviceId": "<serviceId>"
    },
    "name": "attach_domain"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	the full name, for example shop.com: a held name or one attached to another service
`wpSwitch`	No	WordPress sites: the site moves to this name once it answers; default true, false keeps the platform address
`serviceId`	Yes	the id of a service on this account

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"the full name, for example shop.com, from list_services heldDomains"New value: +"the full name, for example shop.com: a held name or one attached to another service"

changedInput schema / properties / serviceId / description

Previous value: -"the service id from list_services"New value: +"the id of a service on this account"

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that the call runs without approval, costs nothing, and moving a name to another service makes the old service stop serving it. It also gives expected certificate timing and specific non-ready/not-deployed failure states, which is valuable operational context.

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 front-loaded with the core action and then efficiently covers timing, side effects, exclusions, and valid name sources. The paragraph is dense because the operation is nuanced, but every sentence adds useful information with no obvious filler.

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?

This is a complex mutating operation with an output schema, and the description supplies the prerequisites, side effects, timing, alternatives, and error states an agent needs. Return-value details are correctly left to the output schema.

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 input schema already documents all three parameters, including name and wpSwitch. The description adds only a small amount of meaning by noting that valid names come from the account's unattached heldDomains and its services' domains; baseline 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: it points a domain bought through the platform at a running deployed service and describes the DNS/certificate mechanics. It also distinguishes this operation from buying a domain and from moving a domain owned at another registrar, which is handled from the dashboard instead.

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?

It clearly states when the tool applies and names explicit exclusions: a domain still registering is not-ready, a service with no deploy is not-deployed, and a connected domain owned elsewhere is moved from the dashboard instead. The same-call reassignment behavior is also called out.

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?