Colab-MCP

Overview Schema Source Related Servers Discussions Admin

colab_job_cancel

Terminate a running background job by sending SIGTERM to its process group, stopping long-running Colab tasks when they are no longer needed.

Instructions

Terminate a running background job (SIGTERM to its process group).

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": {
      "job_id": "<job_id>"
    },
    "name": "colab_job_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes
`session`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 15, 2026

TDQS

B3.4/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 the termination mechanism (SIGTERM to the process group), which is genuinely useful for reasoning about graceful vs. forced shutdown. However, it omits idempotency, error behavior for unknown/finished jobs, and whether the call blocks until exit.

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 the operation and its mechanism; no filler or redundancy.

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?

An output schema exists so return values need no explanation, and the mechanism detail helps. Still missing are the failure/edge-case contract (nonexistent or already-finished job), idempotency, and the meaning of the session parameter for a mutation tool with zero annotation coverage.

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 does not mention either parameter. The optional 'session' argument is entirely unexplained, and there is no hint about job_id format or where to source it (colab_job_start/colab_job_list).

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

Purpose5/5

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

States a specific verb (terminate) and a precisely scoped resource (a running background job), which distinguishes it from the session-scoped colab_stop and from the read-only colab_job_status/colab_job_logs siblings.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as checking colab_job_status first or using colab_job_list to obtain a job_id. The agent must infer the workflow entirely.

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