Skip to main content
Glama

runtime_stop

End a Colab or Kaggle GPU session to stop the Kaggle GPU-hours clock and release the runtime. Save or push results first to preserve outputs.

Instructions

End the Colab/Kaggle session started with colab_runtime_start / kaggle_runtime_start.

Download or push results first (save_checkpoint / hf_push_run). On Kaggle this stops the GPU-hours clock, and the files in /kaggle/working stay on Kaggle as the notebook's output. (A Hugging Face machine is stopped with hf_runtime_stop.)

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": "runtime_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it delivers real behavioral context: stopping halts the Kaggle GPU-hours clock and leaves /kaggle/working files as the notebook output. It implies destructive consequences by warning to save results first, but never states whether Colab-side files are lost or what happens if no session is running.

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?

Four short sentences, front-loaded with the purpose before the precondition and the platform-specific consequence. Every sentence earns its place, including the trailing sibling disambiguation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 with zero parameters and no annotations the remaining burden is behavioral, which is largely met. The notable gap is asymmetry: Kaggle file persistence is spelled out but Colab-side file fate and the no-active-session error case are not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. The description correctly implies the target session is implicit rather than passed as an argument.

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 and resource ('End the Colab/Kaggle session') scoped to sessions created by colab_runtime_start / kaggle_runtime_start. It also names the sibling it is not — 'A Hugging Face machine is stopped with hf_runtime_stop' — so an agent can route correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('Download or push results first (save_checkpoint / hf_push_run)') naming the exact alternatives to call beforehand. It also gives the exclusion case: HF machines use hf_runtime_stop instead.

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