Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Cancel scheduled email

cancel_email
Destructive

Cancel a scheduled or queued email before sending begins so it is never delivered; this action cannot be undone.

Instructions

POST /emails/:id/cancel. Cancels an email that is still "scheduled" or "queued" so it is never sent; this cannot be undone (send it again to deliver it). Once sending has started it can no longer be canceled and the API returns 422 validation_error. A canceled email does not count toward the monthly allowance. Needs a full-access key.

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
idYesThe email id returned when it was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true and idempotentHint=false already declared, the description still adds real value: irreversibility is stated outright, the 422 failure mode is named, billing impact (no monthly allowance charge) is disclosed, and full-access key authorization is required. Only the response body shape is unaddressed, which is minor given no output schema exists.

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 dense sentences, front-loaded with the action and its state constraint, followed by failure mode, billing effect, and auth need. The leading 'POST /emails/:id/cancel' is mild protocol noise but the rest earns its space.

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

Completeness5/5

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

For a single-parameter destructive mutation, the description covers purpose, preconditions, failure behavior, irreversibility, billing, and auth. With annotations carrying the safety profile and no output schema to explain, nothing material 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 coverage is 100% and the single id parameter is already documented as 'The email id returned when it was sent.' The description adds only the REST path showing the id is the targeted resource; baseline 3 is appropriate when the schema carries the semantics.

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 precise verb and resource ('Cancels an email') plus the exact scope: only emails still 'scheduled' or 'queued'. It effectively separates itself from send_email by telling the agent to send again to deliver, so no sibling lookup is needed to understand intent.

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 explicit preconditions (email must still be scheduled or queued), an explicit failure condition (once sending has started the API returns 422 validation_error), and the remediation path (send it again). It does not mention alternatives such as update_scheduled_email for merely changing a pending email, but the when/when-not guidance is otherwise complete.

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