Skip to main content
Glama

clawbridge_cancel

Request cancellation of a remote task by task ID. A successful request is not confirmation; verify a terminal state with clawbridge_refresh before treating the task as canceled.

Instructions

Request cancellation of a remote task. A successful request is not treated as confirmation until clawbridge_refresh observes a terminal state.

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": {
      "taskId": "<taskId>"
    },
    "name": "clawbridge_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose one important trait: success here is only a request, not confirmation of termination. It omits idempotency, behavior for already-finished tasks, required permissions, and what a failed request looks like, which matters for a mutation tool.

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 tight sentences, with the action stated first and the async caveat immediately after. No redundant restatement of the name or filler.

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?

For a single-parameter mutation with no annotations or output schema, the description gives the essential async-safety caveat but leaves the identifier's origin, error behavior, and what to do on repeat calls unexplained. Adequate, not complete.

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 description never mentions the sole parameter. The schema constrains taskId to a UUID pattern but doesn't say which task identifier space it belongs to (local dispatch id vs. remote task id) or where an agent obtains one. The description should compensate for that gap and does not.

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 uses a specific verb and resource ("Request cancellation of a remote task"), so an agent can tell this initiates a cancel rather than performing one. It does not enumerate other cancelling/stopping siblings such as codebuddy_stop_job, so full sibling differentiation isn't achieved.

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?

Usage is implied: use this when you want to stop a remote task. It also points to clawbridge_refresh as the follow-up for confirming termination, which is useful routing. However there is no explicit when-not guidance, e.g. what to do if the task is already terminal or whether an acknowledgement step is needed first.

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