Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete domain

delete_domain
DestructiveIdempotent

Permanently removes a sending domain from a specified pod, requiring pod_id and domain_id. Use it to clean up or decommission domains; the action cannot be undone.

Instructions

Remove a sending domain from the pod. This cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
domain_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is carried structurally; the description adds the explicit irreversibility warning, which usefully reinforces the risk. It does not say what happens to dependent configuration (mailboxes, keys, DNS records) or what happens on a repeated delete despite idempotentHint being set.

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, front-loaded with the action and followed by the single most important consequence. No filler or redundant restatement of the title.

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 two-parameter destructive tool with rich annotations and no output schema, the description covers the essentials of what it does and that it is irreversible. It leaves gaps on the domain_id parameter and on side effects or error behavior, which an agent planning a destructive call would want.

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?

With schema coverage at 50%, the description carries partial burden, yet it explains nothing about domain_id, which is undocumented in the schema. Only pod_id's scope restriction is described, and that text lives in the schema rather than the description, so no meaning is added beyond the structured fields.

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?

States a specific verb and resource ("Remove a sending domain") plus the scope ("from the pod"), which clearly separates it from create_domain, get_domain, and update_domain. It does not name a sibling explicitly, but the verb alone routes the agent unambiguously.

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 mention of alternatives or prerequisites such as verifying the domain is unused. The only implicit cue is that it destroys a domain, which the agent must infer from the verb.

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