Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Send email

send_email

Send one transactional email (OTP, receipt, notification, verification). Provide html with subject, or a template slug with variables. The from domain must be verified. Pass an idempotencyKey (e.g.

Instructions

Send one transactional email (OTP, receipt, notification, verification). Provide html with subject, or a template slug with variables. The from domain must be verified. Pass an idempotencyKey (e.g. the order or user id plus purpose) so that if you retry, the email is not sent twice.

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address, or up to 50 addresses.
fromYesSender, e.g. "Acme <hello@mail.acme.com>". Its domain must be verified (see list_domains).
htmlNoHTML body. Use html OR template, not both.
textNoOptional plain-text body (generated from html if omitted).
replyToNoReply-To address.
subjectNoSubject line (required when sending html).
metadataNoYour own key/values, echoed back in webhooks.
templateNoSlug of a saved template. Use template OR html, not both.
variablesNoTemplate variables.
attachmentsNoUp to 20 files, 10 MB total.
scheduledAtNoISO 8601 time to send later, e.g. 2026-12-25T09:00:00Z.
idempotencyKeyNoSame key = same result, never a second send. Strongly recommended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / attachments
      Added value: +{
      +  "description": "Up to 20 files, 10 MB total.",
      +  "items": {
      +    "properties": {
      +      "content": {
      +        "description": "File bytes, base64-encoded (use this OR path).",
      +        "type": "string"
      +      },
      +      "contentId": {
      +        "description": "Set to embed inline via <img src=\"cid:the-id\">.",
      +        "type": "string"
      +      },
      +      "contentType": {
      +        "description": "MIME type, e.g. \"application/pdf\".",
      +        "type": "string"
      +      },
      +      "filename": {
      +        "description": "Attachment file name, e.g. \"invoice.pdf\".",
      +        "type": "string"
      +      },
      +      "path": {
      +        "description": "HTTPS URL Quolle fetches at send time (use this OR content).",
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "filename"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • changedInput schema / properties / from / description
      Previous value: -"Sender address, e.g. \"Acme <hello@mail.acme.com>\". Domain must be verified."New value: +"Sender, e.g. \"Acme <hello@mail.acme.com>\". Its domain must be verified (see list_domains)."
    • changedInput schema / properties / html / description
      Previous value: -"HTML body (mutually exclusive with template)."New value: +"HTML body. Use html OR template, not both."
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Idempotency key — safe retries never send twice."New value: +"Same key = same result, never a second send. Strongly recommended."
    • addedInput schema / properties / metadata
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Your own key/values, echoed back in webhooks.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / scheduledAt / description
      Previous value: -"ISO 8601 time to send in the future (schedules the email)."New value: +"ISO 8601 time to send later, e.g. 2026-12-25T09:00:00Z."
    • changedInput schema / properties / template / description
      Previous value: -"Slug of a saved template (mutually exclusive with html)."New value: +"Slug of a saved template. Use template OR html, not both."
    • changedInput schema / properties / text / description
      Previous value: -"Optional plain-text body (auto-generated from html if omitted)."New value: +"Optional plain-text body (generated from html if omitted)."
    • changedInput schema / properties / to / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "maxItems": 50,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / variables / description
      Previous value: -"Template variable substitutions."New value: +"Template variables."
    • addedInput schema / properties / variables / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, open-world, not inherently idempotent, non-destructive), and the description adds real context beyond them: the verified-domain precondition and the retry/idempotency contract. It does not cover rate limits, sending quotas, or failure behavior, so it is strong but not exhaustive.

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 tight sentences, front-loaded with the purpose before the parameter rules and the retry constraint. Every sentence carries actionable information with no boilerplate.

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 a 12-parameter, nested-object tool with no output schema, the description covers the primary send paths, the domain prerequisite, and the retry contract. Attachment limits and scheduling are left entirely to the schema, which is acceptable given full coverage, but the omission of failure/error expectations leaves a small gap.

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 description coverage is 100%, so the baseline is 3. The description only restates the html-vs-template exclusivity already documented in the schema, though the idempotencyKey example ('order or user id plus purpose') adds a small amount of practical meaning. Nothing is said about `attachments`, `scheduledAt`, or `metadata`, which the schema handles on its own.

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?

States a specific verb and resource ('Send one transactional email') and immediately scopes it with concrete use cases (OTP, receipt, notification, verification). The word 'one' implicitly separates it from the sibling `send_batch`, so an agent can route without opening either 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?

Gives clear conditional guidance: use `html` with `subject`, or a `template` slug with `variables`, plus the prerequisite that the `from` domain must be verified (pointing at `list_domains`). It also prescribes when to pass `idempotencyKey` (on retry). It does not explicitly contrast with `send_batch` or `cancel_email`, which keeps it below a 5.

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