Skip to main content
Glama

Send approved bulk email

spur_send_bulk_email
Destructive

Queue the exact approved subject/content and recipient set. Show the email preview (spur_preview_message_draft) and audience before approval. Recipients can be mapped CSV rows. Charges email usage; never automatically retry a timed-out send.

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": {
      "subject": "<subject>",
      "recipients": "<recipients>",
      "confirm": "<confirm>"
    },
    "name": "spur_send_bulk_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNo
textNo
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
subjectYes
sender_idNo
recipientsYes
template_idNo
template_kindNo
html_template_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already flag destructive, non-idempotent, open-world behavior, so the description's job is to add context, and it does: it discloses that email usage is charged and that timed-out sends are never automatically retried, which is critical duplicate-send guidance an agent cannot infer from the annotations. It still doesn't say what happens to partially queued recipient lists on failure.

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?

Four short sentences, front-loaded with the core action and followed by the preview prerequisite, cost warning, and retry caveat. Every sentence carries information; nothing is padding.

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?

For a destructive, 9-parameter send tool with no output schema and 11% schema coverage, the description omits too much: how template parameters relate to inline html/text, how sender_id is chosen, and what a successful queue response looks like. The safety-adjacent details it does include are valuable but not sufficient for the tool's complexity.

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?

Schema description coverage is only 11% across 9 parameters, so the description must compensate and largely fails to. It gestures at subject/content, recipients, and CSV row mapping, but says nothing about sender_id, template_id, template_kind, html_template_type, or the html/text versus template interaction.

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 names a specific action on a specific resource: queueing an approved bulk email with its subject/content and recipient set. It distinguishes itself from the preview sibling by naming spur_preview_message_draft, though the verb 'Queue' versus 'Send' in the tool name leaves slight ambiguity about whether dispatch is immediate.

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

Usage Guidelines3/5

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

It implies a workflow (show the preview and audience before approval) and points at the preview tool, which is real guidance. But it never states when not to use this versus spur_send_test_email or spur_send_sms, and the approval prerequisite is only spelled out indirectly in the confirm parameter.

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