Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Cancel task

cancel_task
DestructiveIdempotent

Cancels a task's future execution using its goal ID, expected version, idempotency key, and reason. Emails already accepted for sending cannot be undone.

Instructions

Cancels a task's future execution. An email already accepted for sending cannot be undone.

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": {
      "goal_id": "<goal_id>",
      "expected_version": "<expected_version>",
      "idempotency_key": "<idempotency_key>",
      "reason": "<reason>"
    },
    "name": "cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
goal_idYes
idempotency_keyYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.4/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 the safety profile is covered. The description adds genuine value beyond that by disclosing a partial-irreversibility carve-out: cancellation stops future execution but cannot undo an email already accepted for sending. It does not explain version-conflict behavior or what a successful response contains.

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?

Two short sentences with zero padding, with the core action front-loaded ahead of the risk caveat. Nothing is redundant or buried.

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

Completeness2/5

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

For a destructive, four-required-parameter mutation with no output schema and zero schema coverage, the description is far too thin. It omits concurrency semantics for expected_version, idempotency behavior, and why a reason is required, all of which an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four required parameters, so the schema contributes only names and types. The description never mentions goal_id, expected_version (optimistic concurrency semantics are non-obvious and critical), idempotency_key, or the required reason string, leaving an agent to guess at all four.

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 and resource ('Cancels a task's future execution'), and the phrase 'future execution' narrows scope meaningfully. It does not explicitly distinguish itself from siblings like pause_task, retry_task, or resume_task, so an agent must still infer that cancel is terminal while pause is reversible.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The caveat about an email already accepted for sending implies the boundary of when cancellation is useful, which is real guidance. However, no alternative tool is named and there is no explicit 'use this instead of pause_task when...' routing, so guidance remains implicit.

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

Deploy Server

Other Tools