Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Trash message

trash_message
Idempotent

Moves a message to the trash, keeping it recoverable so inbox cleanup can be undone later.

Instructions

Move a message to trash (reversible with restore_message).

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": {
      "message_id": "<message_id>"
    },
    "name": "trash_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is largely covered. The description adds the genuinely new fact that the operation is recoverable and which tool reverses it, which is the key behavioral detail for an agent deciding to call it.

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?

One short sentence, front-loaded with the action and followed immediately by the recovery path. No filler, nothing to trim.

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 single-parameter tool with annotations carrying the safety and idempotency profile and no output schema to explain, the description covers the essentials. Only the meaning/format of message_id is left implicit.

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 description coverage is 0% and the single parameter message_id has no documentation in either the schema or the description. The description at least establishes that the ID refers to a message, but it adds no format, source, or validity constraints to compensate for the coverage gap.

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?

"Move a message to trash" states a concrete verb and resource, and the parenthetical names restore_message as the undo path. It is clearly distinct from restore_message and implies (without explicitly naming) delete_message, which is the permanent counterpart.

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

Usage Guidelines4/5

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

The mention of reversibility signals when to prefer this over a permanent delete, and it routes the agent to restore_message for undo. It stops short of an explicit when-not statement, but the context needed to pick this tool is present.

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