Skip to main content
Glama

krusch_abort

DestructiveIdempotent

Cancel an in-progress or staged task by task ID. Use it to stop pending work before it applies, so aborted operations are not committed.

Instructions

Cancel and abort an in-progress or staged task.

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": "krusch_abort"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds only the target-state scope; it does not say what happens to the task after abort, whether in-flight work is terminated or merely flagged, whether artifacts are discarded, or whether recovery is possible — meaningful gaps for a destructive mutation.

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 filler, which is appropriate for a simple one-parameter tool. It is efficient but so terse that it leaves the state and parameter ambiguity unaddressed.

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, non-read-only operation with an undocumented required parameter and no output schema, the description should explain the post-abort state and the source of task_id. As written, the agent knows what the tool does nominally but not enough to invoke it safely.

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% and the single required parameter task_id is never mentioned in the description. The agent gets no hint about the identifier's format or where it is obtained (krusch_task_status, krusch_route_task), so the description does not compensate for the schema gap.

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 pairs specific verbs (cancel/abort) with the resource (task) and scopes the target state as 'in-progress or staged,' which is more informative than the title alone. It does not explicitly distinguish itself from the sibling krusch_reject, which an agent might reasonably confuse with cancellation, so it falls short of a 5.

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?

'In-progress or staged' implies the applicable state, giving implied usage guidance, but there is no statement of when not to use it and no named alternative (e.g., krusch_reject, krusch_task_status) for cases where the agent should inspect state or reject rather than abort.

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