Skip to main content
Glama

Remove a Custom Domain

varity_domain_remove
DestructiveIdempotent

Stop serving an app at its custom domain while keeping its Varity web address, allowing the DNS record to be deleted at the registrar.

Instructions

Stop serving an app at its custom domain. The app keeps its Varity web address; the DNS record can then be deleted at the registrar.

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

Input Schema

NameRequiredDescriptionDefault
deploymentYesThe deployment id or app name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

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 meaningful non-annotation context: the deployment survives the operation and keeps its Varity web address, and the DNS record at the registrar is left behind and must be cleaned up manually. It does not state whether the action is reversible or whether re-adding the domain requires re-verification.

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?

Two short sentences, no filler, and the primary effect is front-loaded ahead of the secondary consequence. Every clause conveys distinct information the caller needs.

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 one-parameter destructive tool with full annotation coverage and no output schema, the description covers the key side effects and the manual follow-up step. Only minor gaps remain, such as error behavior when the domain is not configured or whether the operation can be undone.

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?

There is a single required parameter and schema coverage is 100%, with the schema already explaining that it accepts a deployment id or app name and constraining the pattern. The description adds no format, sourcing, or lookup guidance beyond that, so the schema carries the parameter semantics entirely.

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?

"Stop serving an app at its custom domain" gives a specific verb (stop serving) and resource (custom domain), which makes it easy to distinguish from varity_domain_add and varity_domain_verify by implication. It stops short of naming those siblings explicitly, so differentiation relies on the reader's inference rather than direct routing language.

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 rather than stated: the description tells you what happens (the app keeps its Varity address) and what follows (delete the DNS record at the registrar), which sketches a workflow. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for other domain operations.

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