Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create draft

create_draft

Compose a draft reply or new message for human review without sending it; sending is a separate explicit action.

Instructions

Compose a draft reply or new message. This does NOT send — it returns the draft for a human to review; sending is a separate, explicit send_draft call. This is the default write path.

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

Input Schema

NameRequiredDescriptionDefault
ccNo
toNo
textNo
subjectNo
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.
in_reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world write. The description adds the critical behavior beyond that: composing does not transmit, the draft is returned for human review, and this is the default write path. Permission or scope behavior for the inbox is only covered in the schema, not here.

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?

Three short sentences, front-loaded with the action and the send/draft distinction. No filler or restatement of the title.

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?

There is no output schema, and the description says the draft is 'returned' without indicating shape or what identifiers come back for a later send_draft call. Combined with five undocumented parameters, the definition is adequate but leaves real gaps for a six-parameter write tool.

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 only 17% with six parameters, and the description adds no meaning for to, cc, subject, text, or in_reply_to. Only inbox_id carries documentation, and that lives in the schema, so the description fails to 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?

States a specific verb and resource ('compose a draft reply or new message') and immediately distinguishes the outcome from the sibling send_draft. An agent can tell exactly what this tool produces without opening the schema.

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?

Names the alternative ('sending is a separate, explicit send_draft call') and frames this as 'the default write path,' so the routing decision is clear. It stops short of stating conditions under which drafting is inappropriate, but the core when-to-use guidance is present.

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