Skip to main content
Glama

Delete domain

delete_domain
Destructive

Remove a domain from the account. Email can no longer be sent from it.

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": "<domain>"
    },
    "name": "delete_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds the concrete consequence that email can no longer be sent from the domain, which exceeds the annotations. However, it does not say whether deletion is reversible, what happens to existing routes, webhooks or suppressions tied to the domain, or whether in-flight mail fails, which are the most important unknowns for a destructive, open-world delete.

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 with zero filler; the action is front-loaded and the consequence follows immediately. Nothing could be removed without losing information.

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

Completeness3/5

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

For a simple one-parameter tool with annotations covering destructiveness, the definition is close to adequate, and no output schema exists so return values need not be explained. The remaining gap is material though: an agent about to destroy a sending domain in an open-world system should be told whether the action is irreversible and how dependent routes and webhooks are affected.

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 with 100% schema description coverage, including a concrete format example (example.com). The description adds no meaning 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.

Purpose4/5

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

"Remove a domain from the account" states a specific verb (remove) and resource (domain), which is sufficient to distinguish it from delete_route and delete_webhook since those name different resources. It stops short of explicitly contrasting itself with siblings such as delete_route, so it is clear but not maximally differentiated.

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 or when-not-to-use guidance and no stated prerequisites, such as whether the domain must be verified first or whether it must be empty of routes. The consequence sentence describes an effect rather than a selection condition, so usage must be inferred entirely by the agent.

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