Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_agent_cancel_task

Cancels a launched worker request by terminating its recorded process group, ensuring the exact task is stopped and the cancellation reason is recorded.

Instructions

DUAL-GATED: terminate one exact process group recorded by this server.

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": {
      "request_id": "<request_id>"
    },
    "name": "aiworkhub_agent_cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason recorded for the cancellation; default owner_cancelled.owner_cancelled
request_idYesId of the launched worker request whose recorded process group is terminated.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / reason / description
      Added value: +"Reason recorded for the cancellation; default owner_cancelled."
    • addedInput schema / properties / request_id / description
      Added value: +"Id of the launched worker request whose recorded process group is terminated."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, and the description confirms a terminate operation scoped to a recorded process group. However, "DUAL-GATED" remains opaque—no disclosure of what the gates check, whether cancellation is irreversible, or what happens if a gate fails.

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?

A single front-loaded sentence with no wasted words. It is arguably under-specified rather than bloated, but structurally efficient.

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

Completeness3/5

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

With annotations, an output schema, and full parameter descriptions, the baseline is covered. The major omission is any explanation of the "DUAL-GATED" mechanism, which is central to invoking this destructive-adjacent tool correctly.

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%, so both request_id and reason are already documented in the input schema. The description adds marginal value by implying request_id identifies the launched worker request whose recorded process group is terminated, but does not clarify the reason parameter or gate behavior.

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 ("terminate") and resource ("one exact process group recorded by this server"), which distinguishes it from read-only siblings like aiworkhub_agent_list_processes. The "DUAL-GATED" prefix is unexplained and adds ambiguity rather than clarity.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this versus alternatives such as aiworkhub_agent_retry_finalization or other task lifecycle tools. The key term "DUAL-GATED" implies prerequisites but never states what the two gates are or how an agent satisfies them.

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