Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Restore message

restore_message
Idempotent

Restores a trashed email message to the inbox by message ID, recovering deleted messages for continued review or follow-up.

Instructions

Restore a trashed message back to the inbox.

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": "restore_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, idempotent, open-world mutation. The description confirms the state transition back to the inbox, but it does not add details on authorization requirements, failure behavior for non-trashed or missing messages, or whether restored messages retain labels or read state.

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?

A single short sentence with the action and destination front-loaded; no filler or redundancy.

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 one-parameter mutation tool with no output schema, the description covers the core action and destination, and annotations cover safety semantics. It remains thin on prerequisites, permissions, and error outcomes, so it is adequate but not fully complete.

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?

The schema exposes only a message_id string with no description, leaving format undocumented. The phrase "a trashed message" adds a useful validity constraint on which message_id is acceptable, but no ID syntax or example is provided, so it only partially compensates for 0% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description gives a specific verb (Restore) and resource (a trashed message) and states the resulting location (back to the inbox). This clearly distinguishes it from sibling operations such as trash_message and delete_message, even without naming them.

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?

It implies the tool should be used on messages currently in trash to return them to the inbox. It does not explicitly state when not to use it, what alternatives exist, or prerequisites such as required permissions; an agent must infer these from the broader tool set.

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