Skip to main content
Glama

Remove domain

remove_domain
DestructiveIdempotent

Remove a custom domain

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

Input Schema

NameRequiredDescriptionDefault
domain_idYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. The description adds nothing: it does not say whether the domain must be unverified or non-primary first, what the removal detaches from the project, or what the response reports. For a destruction operation it carries almost no behavioral context beyond the flags.

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

Conciseness3/5

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

A single front-loaded sentence with zero waste, but it is thin rather than concise — nothing is over-explained, yet almost nothing is explained. Appropriate size would still be two or three sentences for a destructive operation.

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

Completeness2/5

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

This is a destructive mutation with no output schema, one undocumented required parameter, and several close siblings competing for selection. The definition does not supply enough to call it confidently: preconditions, id-versus-hostname format, and effect of removal are all missing.

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

Parameters2/5

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

Schema coverage is only 50%: project_id has a description (including the use_project session fallback), but domain_id is a bare string with no format. The description does not clarify whether the identifier is a domain id versus a hostname string, nor how it interacts with the project_id/session scoping. It adds essentially no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a clear verb ("Remove") and resource ("custom domain"), but it is essentially an expansion of the name remove_domain and title "Remove domain," adding only the word "custom." It draws no distinction between this and siblings like add_domain, set_primary_domain, or verify_domain, so an agent must infer which domain operation applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated preconditions, and no mention of alternatives such as set_primary_domain (which presumably must happen before removal) or verify_domain. The agent is left to guess the ordering and conflict rules among the domain-management siblings.

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