Skip to main content
Glama
Sign In
colab-drive-mcp

colab-drive-mcp

by YummyTastyCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_local_notebook

Create a new Colab-compatible local notebook. Specify path, optional title, and kernel for immediate use.

Instructions

Create a new Colab-compatible local notebook.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "create_local_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
titleNo
kernel_nameNopython3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description must disclose side effects. It states creation, but does not mention behavior if file exists, permissions needed, or any destructive actions. Minimal behavioral information.

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

Conciseness2/5

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

Description is extremely short (one sentence). While concise, it is under-sized for a tool with three parameters and no schema descriptions, leaving critical information gaps.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters, no annotations, and no output schema, the description is incomplete. It does not specify return value, error conditions, or file creation behavior.

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

Parameters1/5

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

Schema description coverage is 0%. Description adds no meaning to parameters (path, title, kernel_name). It does not explain their roles or requirements beyond the schema.

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?

Description clearly states verb 'Create' and resource 'Colab-compatible local notebook'. It distinguishes from siblings like list_local_notebooks by implying creation vs listing. However, it lacks detail about the file format or location.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like pull_drive_notebook or copy_drive_notebook. The description does not mention prerequisites or typical contexts.

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