Skip to main content
Glama
Vaartix MCP server

Vaartix MCP server

Official
by vaartix-mail

Send email

send_email

Sends one transactional email through Vaartix for login codes, receipts, or notifications, then returns the email ID; confirm sender, recipients, subject, and body first.

Instructions

Send one transactional email (login code, receipt, notification) through Vaartix. Returns the email ID. Before calling, show the user the sender, every recipient, the subject and the body, and get their explicit confirmation. It delivers real email. At most 50 recipients; no attachments.

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

Input Schema

NameRequiredDescriptionDefault
ccNoOne address or a list, e.g. "priya@example.com" or "Priya <priya@example.com>"
toYesOne address or a list, e.g. "priya@example.com" or "Priya <priya@example.com>"
bccNoOne address or a list, e.g. "priya@example.com" or "Priya <priya@example.com>"
fromYesSender on a domain verified in Vaartix, e.g. "Acme <hello@notify.acme.in>"
htmlNoHTML body. Give html, text or both.
tagsNoName/value tags to filter and group emails
textNoPlain-text body. Give html, text or both.
replyToNoWhere replies go: one address or up to 5
subjectYes
scheduledAtNoISO 8601 date-time to send later, e.g. 2026-12-01T09:00:00+05:30
idempotencyKeyNoRetrying with the same key within 24 hours returns the first email instead of sending again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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
    • changedInput schema / 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 / 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"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint, idempotentHint=false, destructiveHint=false), it discloses that real email is delivered, that the user must explicitly confirm sender/recipients/subject/body first, that an email ID is returned, and the recipient/attachment limits. This is exactly the kind of high-stakes side-effect context annotations cannot convey.

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?

Five short sentences, front-loaded with purpose then return value then the safety workflow then limits. Slight redundancy between "Send one transactional email through Vaartix" and "It delivers real email", but the emphasis is arguably justified for an irreversible side effect.

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

Completeness4/5

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

For an 11-parameter mutation with no output schema it covers purpose, return value, safety gating and key limits. Minor gaps remain: it says nothing about what happens on delivery failure or bounce, nor whether scheduledAt sends interact with the recipient cap or the confirmation step.

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?

Schema coverage is 91%, so per-field semantics already come from structured data. The description adds an aggregate recipient cap of 50 across all recipient fields (the schema only caps each field individually) and a negative constraint, no attachments, that the schema cannot express — both are real meaning beyond the schema.

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 names a specific verb and resource ("Send one transactional email") and narrows scope with parenthetical examples (login code, receipt, notification) plus the singular "one", which implicitly separates it from the send_batch sibling. An agent can identify the tool's job without opening the schema.

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 context (single transactional email, not bulk) and a mandatory pre-call workflow: show sender, all recipients, subject and body, then get explicit confirmation. It doesn't explicitly name send_batch or cancel_email as alternatives for multi-message or scheduled sends, so the routing guidance is strong but not exhaustive.

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