Skip to main content
Glama
Vaartix MCP server

Vaartix MCP server

Official
by vaartix-mail

Cancel scheduled email

cancel_email
DestructiveIdempotent

Cancel a scheduled transactional email before it is sent, using its Vaartix email ID. Confirm with the user first; requires a full-access API key or cancel permission.

Instructions

Cancel a scheduled email before it is sent. Confirm with the user first. Needs a full-access API key, or the cancel permission when signed in.

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": {
      "id": "<id>"
    },
    "name": "cancel_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVaartix email ID, e.g. em_7hq2kv9xr4m1c8d3

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety semantics are covered. The description adds genuinely new context not in the structured fields: the required auth level (full-access API key or cancel permission) and the mandatory user confirmation step. It stops short of describing the failure/return behavior, but the additional auth detail is substantive.

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?

Three short sentences with zero filler: action first, then the confirmation prerequisite, then the auth requirement. Each sentence carries distinct, actionable information and nothing is redundant.

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 one-parameter destructive tool whose annotations cover safety and whose schema fully documents the ID, the description covers purpose, precondition and auth. A slight gap remains around what happens on failure or whether a cancelled email can be restored, but nothing critical to calling it correctly is missing.

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% and the single 'id' parameter is already documented with a format pattern and example, so the description need not restate it. The description adds no extra meaning about the identifier beyond the schema, making the baseline 3 appropriate.

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 ('Cancel a scheduled email') and adds a scoping condition ('before it is sent') that distinguishes it from send_email and get_email. An agent can tell immediately that this is a cancellation action on a not-yet-sent email.

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?

'Confirm with the user first' gives an explicit precondition for invocation, which is meaningful guidance for a destructive operation. It does not name alternatives or state when-not to use it (e.g., for already-sent mail), leaving some inference to the agent.

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