Skip to main content
Glama

remove_custom_domain

DestructiveIdempotent

Take a space off its custom domain: the domain stops serving at once and its certificate is released. The space itself, and its spacesheep address, stay as they are. Answers the two DNS records the owner can now delete at their DNS provider.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoThe space whose domain to remove (UUID or link).
hostnameNoOr the domain itself, e.g. docs.acme.com. Pass one of the two.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real value: it says the domain stops serving immediately, the certificate is released, and the space plus its spacesheep address are preserved. It omits permission/auth requirements and reversibility, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the effect and followed by what is preserved and what is returned. The phrase 'Answers the two DNS records' is slightly awkward but carries no waste.

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?

With no output schema, the description usefully discloses the return value (the two DNS records to delete) and the side effects. Combined with annotations and full schema coverage, nothing essential for correct invocation is missing.

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% and both parameters are documented there, including 'Pass one of the two.' The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Take a space off its custom domain') and clearly contrasts with the sibling set_custom_domain/get_custom_domain without needing their schemas. The agent can identify the operation immediately.

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 mutation framing, but the description never names alternatives such as set_custom_domain or get_custom_domain, nor states prerequisites (e.g. domain must currently be attached). The agent must infer when this is the right call.

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