Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Reply to message

reply_message
Destructive

Sends an immediate email reply to the original sender of a received message, bypassing drafts. Use only when direct-reply permission is granted, since the sent email cannot be undone.

Instructions

Reply to a received message directly, without a draft. This sends email to the original sender and cannot be undone. Prefer create_draft -> send_draft for human review; this tool exists only for keys the human granted direct-reply.

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

Input Schema

NameRequiredDescriptionDefault
textNo
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

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description's job is lighter. It still adds useful context beyond them: delivery goes to the original sender specifically, and the action cannot be undone, which clarifies the blast radius of a non-idempotent send.

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 sentences, no waste, with the action and irreversibility front-loaded ahead of the alternative-route guidance. Every clause earns its place.

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?

The irreversible outbound send is well framed, but for a 3-parameter tool with low schema coverage and no output schema, an agent still lacks any explanation of what `text` and `message_id` should contain. Adequate for routing, incomplete for correct invocation.

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 coverage is only 33%, and the description never mentions the `text` parameter at all, leaving the message body's semantics undocumented in both places. Only inbox_id carries a schema description (scope enforcement); message_id is likewise unexplained, so the description does not compensate for the coverage gap.

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?

"Reply to a received message directly, without a draft" states a specific verb (reply) and resource (received message) and immediately distinguishes the tool from the draft-based path. An agent can tell it apart from create_draft/send_draft without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the preferred alternative flow (create_draft -> send_draft for human review) and the narrow condition under which this tool is appropriate (keys the human granted direct-reply). Both the when and the when-not are stated.

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