Skip to main content
Glama

colab_cancel_job

DestructiveIdempotent

Cancel a queued or running Colab compute job by its job ID to stop execution and release resources.

Instructions

Cancel one of this client's queued or running Colab jobs.

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": {
      "jobId": "<jobId>"
    },
    "name": "colab_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, so safety semantics are covered structurally. The description adds the useful constraint that only queued or running jobs are cancellable, but omits what happens to artifacts/outputs, whether cancellation is graceful, and error behavior for already-completed jobs.

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?

A single front-loaded sentence with no filler; the scope and state qualifiers appear before any other information. Nothing could be removed without losing meaning.

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 simple one-parameter mutation tool with no output schema, the definition is serviceable, with annotations covering idempotency and destructiveness. It still leaves open post-cancel outcomes (return value, terminal state of the job) that an agent would want before invoking it.

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?

With only one parameter and 0% description coverage in the schema, the description carries some burden; it clarifies the jobId must belong to this client and be in a cancellable state. However, it adds nothing about where to obtain the ID or format expectations beyond what the schema's uuid pattern already encodes.

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 (cancel) and resource (Colab jobs), plus a scope qualifier (this client's, queued or running) that already separates it from colab_run_job and colab_job_status. It does not explicitly name a sibling to route against, so it falls just 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?

The phrase 'queued or running' implies the valid state for cancellation, but the description never says when to choose this over colab_pool_stop or what to do for jobs in other states. Usage is inferable rather than stated.

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