Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Cancel a scheduled email

cancel_email
DestructiveIdempotent

Cancel a scheduled email before it is sent by providing its ID, stopping unsent messages when plans change.

Instructions

Cancel a scheduled email that has not been sent yet.

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 scheduled email's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / id / description
      Previous value: -"The scheduled email's ID."New value: +"The scheduled email's id."
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is covered. The description usefully adds the precondition that only unsent emails qualify, but says nothing about what happens on an already-sent or invalid id, nor whether cancellation is reversible.

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?

One sentence, front-loaded with the action and immediately qualified by the precondition. Nothing is wasted and nothing essential is buried.

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 mutation with rich annotations and no output schema, the description covers purpose and eligibility adequately. The only gap is failure behavior for already-sent emails, which is minor given the annotation coverage.

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% with a single documented 'id' parameter, so the schema carries the semantics. The description adds no extra guidance on the id (format, where to obtain it), which is acceptable at this baseline.

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?

States a specific verb+resource ('Cancel a scheduled email') and adds the eligibility scope ('has not been sent yet'), which distinguishes it from send_email/get_email by intent. It does not explicitly name a sibling, but the action is unambiguous against the listed tools.

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?

The clause 'that has not been sent yet' gives a clear precondition for when this tool applies, which is the main usage decision an agent faces here. No explicit alternatives or exclusions are named (e.g. what to do for an already-sent email), keeping it short of a 5.

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