Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete message

delete_message
DestructiveIdempotent

Permanently remove a message from a permission-scoped inbox by specifying its inbox ID and message ID; this action cannot be undone.

Instructions

Permanently delete a message. 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": {
      "inbox_id": "<inbox_id>",
      "message_id": "<message_id>"
    },
    "name": "delete_message"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 irreversibility warning in the description largely restates structured data. It adds no context about cascade effects (e.g., whether the thread is affected), required permissions, or what a successful response looks like.

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

Conciseness4/5

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

Two short sentences, front-loading the action and following with the irreversible consequence. No filler, though the second sentence duplicates a behavior already conveyed by the destructive annotation.

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 delete with full safety annotations and no output schema, the core is covered. Still missing is any hint about whether a message must be trashed first, whether related thread data is affected, or what the call returns, which matters for an irreversible operation.

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?

The description adds no meaning about either parameter, and schema coverage is only 50% — inbox_id is documented in the schema (including the scope-rejection rule) but message_id is completely bare in both places. With half the parameters undocumented and no compensating detail in the description, the definition leaves real ambiguity about what message_id accepts.

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?

The description states a specific verb and resource ('Permanently delete a message') and the word 'permanently' implicitly separates it from the sibling trash_message, which is recoverable. It does not name that sibling outright, so an agent must still infer the contrast from the permanence cue rather than being told directly.

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?

When-to-use is only implied: the tool is for irreversible removal, so an agent should prefer trash_message when recovery may be needed. No explicit when-to-use, prerequisites, or named alternative is given, leaving the trash-vs-delete routing decision to inference.

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