Skip to main content
Glama
uth-mail-mcp

uth-mail-mcp

by fotispetrou

send_draft

Destructive

Sends an email draft from the Drafts folder and files a copy in Sent, but only after you show the draft to the user and receive clear confirmation.

Instructions

Send a draft from the Drafts folder and file a copy in Sent. This really sends email: call it only after showing the user that draft (recipients, subject and text) and getting a clear yes for it.

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": {
      "uid": "<uid>"
    },
    "name": "send_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the danger profile is known. The description still earns credit by adding non-obvious context: the message is genuinely transmitted ("This really sends email") and a copy is filed in Sent, which is a side effect not encoded in annotations. It does not describe failure behavior, e.g. what happens if the uid is invalid or the draft is empty.

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 tightly written sentences with the action stated first and the safety precondition immediately after. No filler or repetition.

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 one-parameter destructive tool with no output schema, the description covers the essential elements: what happens, the irreversible external effect, and the required user confirmation. Only the missing explanation of the uid argument and the error path keep it from being 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?

There is a single required parameter, uid, but schema description coverage is 0% and the description never mentions it or how to obtain a draft identifier. A 3 reflects that the meaning is inferable from "send a draft" but not actually explained beyond the schema.

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?

Uses a specific verb and resource ("send a draft") and states the resulting side effect ("file a copy in Sent"). It is clearly distinct from the sibling create_draft by implying the draft already exists, though it never names an alternative.

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?

Gives an explicit precondition for invocation: show the user the draft's recipients, subject and text and receive a clear yes. That is a strong when-to-call gate, but it offers no guidance on what to do instead when the user has not yet created a draft (e.g. the create_draft sibling).

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