Skip to main content
Glama

colab_pool_stop

DestructiveIdempotent

Stop idle Colab VMs by session name; use force to cancel this client's jobs on selected VMs during shutdown.

Instructions

Stop idle VMs, optionally by session name. Force can also cancel this client's jobs on selected VMs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "colab_pool_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
sessionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: force has a second effect, cancelling this client's jobs on the selected VMs, which is not obvious from the annotations.

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 short sentences, front-loaded with the primary action and followed by the parameter-dependent side effect. No filler or repetition.

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?

With no output schema and a destructive, open-world operation, the description covers the core action and the main side effect but leaves gaps: the default for force, what happens to running jobs on stopped VMs, and what the call returns or confirms.

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?

Schema description coverage is 0% across two parameters, so the description must carry meaning. It explains that sessionName is an optional selector and that force widens behavior to job cancellation, but it omits defaults (notably what force defaults to) and does not clarify whether jobs on stopped VMs are always affected.

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 states a specific verb and resource ('Stop idle VMs') plus a scoping detail ('optionally by session name'), making the operation identifiable. It does not explicitly contrast itself with siblings like colab_cancel_job, but the VM-oriented purpose is clear.

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 word 'idle' implies the intended condition (only idle VMs should be stopped), and 'optionally by session name' indicates narrowing scope. There is no explicit when-not guidance or named alternative for cancelling jobs instead of stopping VMs.

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