Skip to main content
Glama
yahoo-mail

yahoo-mail

by soothslayer

send_message

Idempotent

Send a plain-text email through Yahoo Mail with allow-list enforcement, hourly limits, and idempotency keys to avoid duplicate sends during retries.

Instructions

Send a user-authorized plain-text email. This has an external side effect.

Recipients are plain email addresses. Supply a unique key (e.g. UUID) for each intended email, and reuse the SAME key and content for retries. unknown means possibly sent: never retry with a new key. accepted means SMTP accepted it, not guaranteed delivery. in_reply_to takes the original internet_message_id, NOT the opaque search result ID. Sends are refused for recipients outside the config's allow-list when one is set, and are capped at max_sends_per_hour sends per hour.

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>",
      "body": "<body>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
subjectYes
in_reply_toNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses external side effects, allow-list refusal behavior, hourly send caps, retry semantics, and the specific meaning of uncertain delivery states. These are exactly the behavioral details an agent needs before invoking a sending tool.

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?

The description is front-loaded with the action and side effect, then moves through parameter-critical semantics and failure/retry rules. Every sentence carries operational value and there is no filler.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers the critical context: external side effect, authorization posture, rate limiting, allow-list restrictions, retry safety, delivery-state interpretation, and the non-obvious in_reply_to identifier requirement. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds substantial meaning: recipients must be plain email addresses, idempotency_key must be unique per intended email and reused on retries, and in_reply_to requires the original internet_message_id rather than the opaque search result ID. Standard cc/bcc fields are not individually explained, which keeps it from a 5.

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 description states a specific verb and resource: send a user-authorized plain-text email. It immediately distinguishes this from read/search siblings by calling out the external side effect.

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?

It gives clear operational guidance for retries, idempotency keys, and what unknown versus accepted mean. It does not explicitly name alternative tools or when not to use this one, so it stops short of full alternative routing guidance.

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