Skip to main content
Glama

colab_runtime_start

Prepare a Google Colab session by returning the exact line to run in Colab; then connect the runtime so the session is located automatically.

Instructions

Prepare a Google Colab session. Returns one line for the user to run in Colab.

Google does not let a program start a Colab session, so the user does two things: open a notebook and run the line. Nothing is copied back: when the line is running, call connect_runtime and the session is found automatically. Show the user the steps exactly as returned.

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_runtime_start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the platform limitation, that no session identifier is copied back, that the session is auto-discovered by connect_runtime, and that the output must be shown verbatim to the user. It stops short of covering repeated invocations, session lifetime, or failure modes.

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

Conciseness4/5

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

Front-loaded purpose sentence, then the constraint, then the handoff, then the verbatim-display instruction — a logical order with little waste. The multi-line formatting is slightly awkward but every sentence carries a distinct fact.

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?

For a zero-parameter tool with an output schema and no annotations, the description covers the whole interaction loop: what it returns, what the user must do, and which sibling to call next. Only edge cases (repeat calls, expiry) are absent, which is minor at this complexity.

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 nothing for the description to disambiguate and the baseline applies. The prose correctly implies no arguments are needed.

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 action on a specific resource (prepare a Google Colab session) and immediately says what comes back (one line for the user to run). The Colab naming also separates it from the hf_runtime_start and kaggle_runtime_start siblings without needing their schemas.

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 sequence: call this tool, show the user the returned steps, then call connect_runtime once the line is running. It also explains the constraint that forces this two-step flow (Google does not allow programmatic session start), so the agent knows why not to look for a one-call alternative.

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