Skip to main content
Glama

aw.jobs.cancel

Retire active work AND in-flight uploads that have not committed. Completed immutable inputs/artifacts are not deleted. Stable upload UUID/operationId reconcile committed receipts. Bounded32 cancellation requests remain available after ordinary quota exhaustion; close clears active copies.

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": {
      "session": "<session>"
    },
    "name": "aw.jobs.cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes meaningfully beyond that by declaring the blast radius: committed immutable inputs/artifacts are NOT deleted, and close clears active copies. It also discloses a real operational trait — bounded cancellation requests survive ordinary quota exhaustion — which is exactly the kind of context annotations cannot carry. The 'Stable upload UUID/operationId reconcile committed receipts' clause is too cryptic to count fully, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core action, and every sentence carries some information. But the later sentences are compressed into near-unparseable jargon ('Bounded32', 'reconcile committed receipts'), trading clarity for brevity rather than genuinely earning concision. A reader has to decode rather than read.

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 output schema, the description covers the important question of what survives cancellation, which is the key risk information. It omits whether the call is idempotent, what a cancelled job's state becomes afterward, and how the session capability relates to the cancellation. Adequate but with clear gaps for a destructive-adjacent operation.

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?

There is a single parameter, session, and schema description coverage is 100% with a pattern and an explicit 'never publish or log it' warning already in the schema. The description adds nothing about the session capability or its lifecycle, so the schema is doing all the work. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a concrete action and scope: 'Retire active work AND in-flight uploads that have not committed.' That is a real verb-and-resource statement an agent can act on. However, the term 'Retire' plus the dense follow-on clauses ('Stable upload UUID/operationId reconcile committed receipts', 'Bounded32 cancellation requests') obscure the plain purpose of cancelling a job, and nothing distinguishes it from siblings such as aw.input.abort or aw.session.close.

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?

The description implies the applicable situation (work is active or uploads have not committed) but never states when to call this versus aw.input.abort or aw.session.close, both of which plausibly overlap. The one routing-adjacent statement — cancellation remains available after quota exhaustion — is about availability, not about choosing this tool over another. An agent gets no explicit when/when-not guidance.

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