Skip to main content
Glama
Sign In
cfu_mail

cfu_mail

by MrShurukan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

prepare_draft

Saves a plain-text email draft to the server and generates an immutable local preview without sending it, letting you review the message before transmission.

Instructions

Save a plaintext server draft and immutable local preview. Does not send.

No attachments in this version. A changed message requires a new draft.

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": {
      "account_id": "<account_id>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "prepare_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
subjectYes
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint false, destructiveHint false), the description adds meaningful behavior: it saves a server draft and an immutable local preview, does not send, lacks attachment support, and requires a new draft for any changed message. These are valuable operational constraints not captured by annotations.

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?

The description is three short sentences with no wasted words, and the core action is front-loaded. It could be slightly more structured by explicitly listing parameter expectations, but it is appropriately concise.

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?

Given four required parameters, no output schema, and open-world write behavior, the description covers purpose and key constraints but leaves parameter semantics entirely unexplained. It is adequate but has clear gaps for an agent needing to form a 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 description coverage is 0% for all four required parameters. The description only hints that the body is plaintext, but gives no information about 'to', 'subject', or 'account_id' beyond what is in the schema names. It fails to compensate for the lack of schema documentation.

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 uses a specific verb and resource: 'Save a plaintext server draft and immutable local preview.' It distinguishes itself from send_draft by stating 'Does not send,' and from preview_draft indirectly through 'local preview' being part of the save operation. However, the relationship with preview_draft is not explicitly clarified.

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?

The description implies usage context ('Does not send,' 'No attachments in this version'), but it does not explicitly say when to use this tool versus alternatives like preview_draft or send_draft. The guidance is present but relies on inference.

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

Deploy Server

Other Tools