Provision or reuse a Colab GPU runtime (L4 default) for running scripts and managing Drive checkpoints. Confirms Drive mount and tracks Colab unit consumption.
Provision or reuse the configured runtime. Default GPU is L4. Consumes Colab units.
If drive_mounted is false, run colab-persist mount in a user terminal to authorize Drive.
| Name | Required | Description | Default |
|---|---|---|---|
| gpu | No |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses cost (Colab units) and the default GPU, which is useful, but omits other behaviors like idempotency, async behavior, or side effects beyond cost. For a provisioning tool, this is partial disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. The core purpose and default are front-loaded, and the conditional instruction is necessary and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the main action, default GPU, cost, and a prerequisite. It does not describe return values or how to verify success, but given the simplicity and lack of output schema, this is reasonably complete. It could mention whether it blocks or returns immediately, but overall it's adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate. It mentions 'Default GPU is L4', which clarifies the default for the optional gpu parameter, but does not enumerate valid values or explain what null means beyond the default. An agent would not know what strings to pass (e.g., 'T4', 'A100').
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Provision or reuse' with the resource 'runtime', and mentions the default GPU and cost. This clearly distinguishes it from siblings like runtime_status (status check) and safe_stop (stop), so an agent can select it appropriately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear conditional prerequisite (if drive_mounted is false, run a specific mount command) and mentions that it consumes Colab units. It does not explicitly name alternatives, but the action and context are clear enough to imply when to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.