Skip to main content
Glama

Disconnect a custom domain

disconnect_domain
DestructiveIdempotent

Removes a custom domain from a site. The site keeps working at its free mywebdesk.app address. The owner can remove the DNS records at their domain provider afterwards.

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": {
      "site_id": "<site_id>",
      "hostname": "<hostname>"
    },
    "name": "disconnect_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.
hostnameYesThe domain to connect, for example www.joesplumbing.com.au. Use a www or other subdomain, not a bare domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the site remains functional at its free address after removal, and DNS records must be cleaned up out-of-band at the domain provider — an important external side effect an agent should surface to the user.

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?

Three short sentences, front-loaded with the action, then the resulting state, then the follow-up obligation. No redundant restatement of the title or annotations; every sentence carries information.

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?

For a two-parameter mutation with full schema coverage, no output schema and rich annotations, the description covers the essential post-conditions. It stops short of stating whether the disconnect takes effect immediately or whether DNS removal is required versus optional, which would close the remaining gap.

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 coverage is 100%, so site_id and hostname are already fully documented, and the description adds no additional meaning about their format or constraints. Baseline 3 applies since the schema does all the parameter work.

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?

Opens with a specific verb and resource: "Removes a custom domain from a site." An agent can immediately distinguish this from the connect_domain sibling by the removal verb, though the description never names the counterpart tool 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?

Usage is implied by the described outcome (site reverts to its free mywebdesk.app address), but there is no explicit when-to-use versus check_domain/connect_domain guidance, nor any stated prerequisite such as verifying the domain is currently attached.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources