Skip to main content
Glama
Vaartix MCP server

Vaartix MCP server

Official
by vaartix-mail

Send batch

send_batch

Sends up to 20 transactional emails in a single call and returns their IDs in order, enabling batch delivery after the user confirms sender, recipients, subject, and body.

Instructions

Send up to 20 transactional emails in one call. Returns their IDs in order. Before calling, show the user the sender, every recipient, the subject and the body, and get their explicit confirmation. It delivers real email.

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": {
      "emails": "<emails>"
    },
    "name": "send_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYes
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / emails / items / additionalProperties
      Added value: +false
    • changedInput schema / properties / emails / items / properties / replyTo / anyOf
      Previous value: -[
      -  {
      -    "minLength": 3,
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "minLength": 3,
      -      "type": "string"
      -    },
      -    "maxItems": 50,
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "minLength": 3,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "minLength": 3,
      +      "type": "string"
      +    },
      +    "maxItems": 5,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / emails / items / properties / replyTo / description
      Previous value: -"One address or a list, e.g. \"priya@example.com\" or \"Priya <priya@example.com>\""New value: +"Where replies go: one address or up to 5"
    • changedInput schema / properties / emails / maxItems
      Previous value: -100New value: +20
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already flag openWorldHint=true and idempotentHint=false, and the description usefully reinforces the external, real-world effect ('It delivers real email') and the human-approval requirement. However, it says nothing about partial-batch failure behavior or the idempotencyKey retry story, which matters given idempotentHint=false.

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?

Four short sentences, front-loaded with capability and limit, then the confirmation requirement, then the real-send warning. Nothing is padded or redundant.

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 destructive-in-the-real-world mutation with no output schema, the confirmation workflow and ID-return order are well covered. Batch failure semantics and the unused idempotencyKey remain gaps an agent would want before wiring this into an automated flow.

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 reported at 0%, so the description should carry meaning, yet it only restates the array cap of 20 and the ordered return of IDs. It never mentions the idempotencyKey parameter at all, leaving safe-retry semantics entirely unexplained.

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 gives a specific verb and resource ('Send ... transactional emails') plus a hard scope ('up to 20 ... in one call'), which implicitly separates it from the single-send sibling send_email. It stops just short of naming the alternative outright.

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 provides a concrete pre-flight protocol: show the sender, every recipient, subject and body, then obtain explicit confirmation. What is missing is guidance on batch versus single send, i.e. when to choose send_batch over send_email.

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