Skip to main content
Glama

send_email

Send an email to a vendor or counterparty to request a corrected invoice, dispute price or quantity, confirm delivery or bank details, or ask a general accounts-payable question.

Instructions

Send an email. Replies arrive the next day. intent tells the recipient what you are asking for; body is your free-text message.

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>",
      "intent": "<intent>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyNo
intentYes
invoice_idNoThe invoice the email is about, if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It helpfully notes that replies arrive the next day, implying asynchronous, non-immediate resolution, but says nothing about whether a send is irreversible, whether it can be recalled, what permissions are needed, or whether repeated sends are possible. For an outbound-communication mutation this leaves key behavioral risk undisclosed.

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?

Three short sentences, front-loaded with the action, with no filler. The note about replies arriving the next day is slightly tangential to invocation but is short and informative enough to keep.

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

Completeness2/5

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

With no annotations and no output schema, the description should say what a successful send returns (e.g., a message identifier) and what failure looks like. It also leaves recipient format and the linkage between invoice_id and the intent enum undefined, which matters for a four-parameter tool with only two required fields.

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 only 25%, with invoice_id being the only documented property, so the description must compensate. It does explain the role of `intent` (what you are asking for) and `body` (free-text message), which is genuinely additive beyond the bare enum and string types, but `to` gets no format guidance and the relationship between invoice_id and intent is left implicit.

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 opens with a specific verb and resource ("Send an email") that separates it from siblings like read_email, list_inbox, or call_vendor. It clearly conveys the action and briefly names the two payload fields. It stops short of stating scope (single recipient vs. bulk, internal vs. external).

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?

There is no guidance on when to send an email rather than use call_vendor or request_approval, and no prerequisites or exclusions are given. The agent must infer the appropriate situation from the description alone.

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