Skip to main content
Glama

Ellimist

Cancel queued work (free)

cancel_task

Cancel a task that is still queued, using the cancel_token from its access block. The payment authorization is released and nothing is charged. Free.

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": {
      "task_id": "<task_id>",
      "cancel_token": "<cancel_token>"
    },
    "name": "cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
cancel_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a mutation that is not destructive; the description adds important context that payment authorization is released and nothing is charged. It does not cover irreversibility or error behavior, but adds meaningful value beyond the annotations.

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?

The definition is three short, front-loaded sentences with no structural waste. The final 'Free.' slightly repeats the title's '(free)' but is not disruptive.

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 simple two-parameter cancellation tool, the description covers the queued-only condition, token source, and billing effect. It omits return/error behavior, which is a modest gap given there is no output schema.

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?

With 0% schema description coverage, the description must carry parameter meaning. It explains where the cancel_token comes from, but gives no detail on task_id semantics, token format, or token expiry.

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?

The description states a specific verb and resource ('Cancel a task') and narrows scope to tasks 'still queued.' It clearly distinguishes the operation from read-only siblings like get_task, though it does not explicitly name an alternative.

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?

It states the key condition for use ('still queued') and the prerequisite ('cancel_token from its access block'), implicitly excluding running or completed tasks. It does not explicitly describe what to do when the task is not queued or name an alternative workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources