Skip to main content
Glama
Sign In
@qirabot/mcp

@qirabot/mcp

by qirabot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_task

Cancels a task that is pending or running. Does not affect completed tasks.

Instructions

Cancel a task that is currently in 'pending' or 'running' status. Has no effect on tasks that have already completed (succeeded, failed, timeout).

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so description bears full burden. It discloses that cancel has no effect on completed tasks, but does not detail potential side effects (e.g., irreversibility, immediate vs. queued). Still adds useful behavioral context.

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 sentences, direct and devoid of fluff. Every word serves a purpose.

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?

No output schema, but description hints at no output for completed tasks. Could mention return value or success confirmation, but overall sufficient for a simple cancel action.

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 covers 100% of parameters with description, meeting baseline. Description adds no extra meaning beyond 'the task ID to cancel'.

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?

Description clearly states the tool cancels a task, specifying valid statuses ('pending', 'running') and ineffectiveness on completed tasks. This distinguishes it from sibling tools like 'get_task' (read) and 'run_task' (create).

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?

Provides clear when-to-use guidance (pending/running tasks) and when-not-to (completed tasks). Does not explicitly mention alternative tools, but siblings are implied.

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