Skip to main content
Glama
Sign In
Colab MCP

Colab MCP

by ALiwoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_colab_browser_connection

Connects to a Colab notebook in your browser to unlock its notebook tools; if disconnected, opens a scratch notebook or supplied URL and waits up to 60 seconds.

Instructions

Connect to a Colab notebook in the browser and unlock its notebook tools. When disconnected, opens a scratch notebook or the supplied notebook_url. Waits up to 60 seconds for a connection. The optional Chrome companion accepts the matching MCP connection prompt automatically.

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

Input Schema

NameRequiredDescriptionDefault
notebook_urlNoExisting HTTPS Colab notebook URL.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/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 a 60-second wait, the scratch-notebook fallback when no URL is given, and that the Chrome companion auto-accepts the MCP connection prompt. Gaps remain on failure/timeout behavior and what state is left behind if the connection drops.

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?

Four tight sentences, front-loaded with purpose, then fallback behavior, then the timeout, then the companion automation. Nothing is padded, though "unlock its notebook tools" is slightly hand-wavy phrasing that could be more concrete.

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 not be explained, and the single parameter is described in the description. For a side-effecting connection tool with zero annotations, the timeout and companion-auto-accept details cover most of what an agent needs, with error handling the notable omission.

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 coverage is 100% and the single parameter is documented as an existing HTTPS Colab URL, so the baseline is 3. The description adds real value by explaining that omitting it opens a scratch notebook, which is not derivable from the schema alone.

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?

"Connect to a Colab notebook in the browser and unlock its notebook tools" names a specific verb, resource, and downstream effect. However, it never distinguishes itself from the sibling tool `connect_colab_tab`, which sounds near-identical in purpose, leaving real ambiguity for tool selection.

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 description supplies conditional behavior ("When disconnected, opens a scratch notebook or the supplied notebook_url"), which implies when the tool applies, but it never states when to prefer this over `connect_colab_tab` or `list_colab_tabs`, nor prerequisites such as a running Chrome companion.

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