Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete inbox

delete_inbox
DestructiveIdempotent

Permanently delete a permission-scoped inbox by its ID, removing the address for good. The address is tombstoned and never reused, so deletion cannot be undone.

Instructions

Delete an inbox. This cannot be undone and the address is never reused (tombstoned).

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": {
      "inbox_id": "<inbox_id>"
    },
    "name": "delete_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description still adds real value by explaining that the deletion is irreversible and that the address is tombstoned and never reused. It does not mention permission requirements or what happens to messages already in the inbox.

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 the action first and the irreversible consequence immediately after. There is no redundant or filler wording.

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 whose annotations already signal destructiveness and idempotency, the description covers the key irreversible consequence. It leaves open what happens to existing messages or whether deletion is blocked when the inbox is non-empty, which is a modest but real gap.

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 coverage is 100%, and the inbox_id description already explains that it must come from list_inboxes and that out-of-scope ids are rejected. The description contributes nothing further about the parameter, so the baseline 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?

A specific verb plus resource: 'Delete an inbox' states exactly what the tool does. The tombstoning note further clarifies the scope of the operation, though the description never distinguishes this from siblings such as update_inbox or delete_domain.

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: nothing says under what conditions an inbox should be deleted rather than updated or left alone, and no alternative tool is named. The reader must infer both the context and any preconditions from the name alone.

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