Skip to main content
Glama

Agent Email Transactional Dispatcher (x402)

agent_send_email

Dispatches transactional or alert emails on behalf of an autonomous AI agent. Automatically compiles Markdown into responsive HTML emails (0.005 USDC via x402 on Base).

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email address (or comma-separated list of recipients)
htmlNoOptional raw HTML body override
textNoOptional plain text body fallback
replyToNoOptional Reply-To email address
subjectYesEmail subject line
markdownNoMarkdown email content (automatically compiled into responsive HTML email)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: Markdown is auto-compiled into responsive HTML and each send costs 0.005 USDC via x402 on Base. It omits delivery semantics (queued vs. sent, failure/retry behavior, credential requirements), which matter for a paid side-effecting call.

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, zero filler, with the core action front-loaded and the cost/rendering detail following. Nothing could be cut without losing information.

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?

For a six-parameter, paid, non-idempotent send operation with no output schema, the definition covers purpose and cost but leaves success/failure outcomes and body-field precedence unexplained. Adequate to invoke, not sufficient to invoke confidently.

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?

Schema coverage is 100%, so every parameter is already documented, and the description's note about Markdown compilation merely restates the 'markdown' field description. It does not clarify the important ambiguity of precedence among markdown, html, and text when multiple body fields are supplied.

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 states a specific verb and resource ('Dispatches transactional or alert emails') plus the operating context (an autonomous AI agent), which is far more informative than the bare tool name. It does not explicitly contrast with the sibling agent_preview_email, so the agent must infer the send-vs-preview distinction from names alone.

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

Usage Guidelines2/5

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

It narrows the intended use to transactional or alert email, but gives no explicit when-to-use/when-not guidance and never mentions previewing first via agent_preview_email. An agent has to infer the workflow rather than being routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources