Skip to main content
Glama
Sign In
Colab MCP

Colab MCP

by ALiwoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

runtime_status

Read-only

Reports whether the Chrome companion is connected, the current Colab runtime state and settings, and the last runtime operation. Use it to confirm completion after runtime_action.

Instructions

Report whether the optional Chrome companion is connected, the current Colab runtime state and settings, and the last runtime operation. Use this to check completion after runtime_action.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

readOnlyHint=true is consistent with a tool named runtime_status that only reports. The description adds useful context that the Chrome companion is optional (so absence of a connection is normal, not an error) and that the 'last runtime operation' is included. It does not describe return shape or how stale the state may be, but annotations already carry the safety profile.

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 sentences, zero filler, with the reported content front-loaded before the usage pointer. Every clause earns its place.

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?

With no output schema, the description carries the burden of saying what comes back, and it names all three reported items. It is slightly thin on the form of those values (e.g., possible runtime state names), but for a no-parameter read-only status tool it is essentially complete.

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 and the schema has additionalProperties false, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description correctly implies no inputs 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 verb (report) and enumerates exactly what is reported: Chrome companion connection status, Colab runtime state and settings, and the last runtime operation. This clearly distinguishes it from the sibling runtime_action, which mutates state.

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

Usage Guidelines4/5

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

Gives explicit when-to-use guidance: 'Use this to check completion after runtime_action,' which names the sibling and the triggering condition. It stops short of stating when not to use it or mentioning transfer_status/list_colab_tabs as alternatives for adjacent status queries.

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

Deploy Server

Other Tools