Skip to main content
Glama
CSOAI-ORG

Email Automation MCP

create_draft

Save an email as a draft without sending. Specify recipient, subject, and body; the draft appears in your Drafts folder for future dispatch.

Instructions

Save an email as a draft without sending it. The draft appears in your Drafts folder and can be sent later from your email client.

Args: to: Recipient email address subject: Email subject body: Email body text

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results. Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
subjectYes
bodyYes
api_keyNo
Behavior1/5

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

The 'Behavioral Transparency' section claims the tool is read-only with no side effects, but saving a draft inherently modifies state. This contradicts the tool's actual behavior. The detailed security/rate-limit information is copied from a different type of tool and does not fit an email draft creator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy and contains irrelevant sections (e.g., behavioral transparency for a different tool). Information is repeated and not front-loaded. The first paragraph is concise, but the rest is unnecessary and misleading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, no output schema, and no annotations, the description fails to provide complete guidance. It does not explain how to use the tool, what the response looks like, or what happens after saving. The contradictory sections make it unusable.

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?

The description lists 'to', 'subject', 'body' in the Args section but provides no format, constraints, or examples. The 'api_key' parameter is not mentioned. With 0% schema description coverage, the description adds minimal value beyond parameter names.

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 first sentence clearly states 'Save an email as a draft without sending it', specifying the verb (save), resource (draft), and distinct action (not sending). This distinguishes it from 'send_email' among siblings.

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

Usage Guidelines1/5

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

The 'When to use' section is generic and unrelated ('structured analysis or classification'), and the 'When NOT to use' mentions 'real-time production decision-making', which does not apply to drafting emails. These sections are misleading and contradict the tool's purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/email-automation-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server