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

colab-drive-mcp

by YummyTastyCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

copy_drive_notebook

Copy a Google Drive notebook file without executing it. Specify the file ID and new name to create a duplicate in Drive.

Instructions

Copy a notebook file in Google Drive without executing it.

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": {
      "file_id": "<file_id>",
      "name": "<name>"
    },
    "name": "copy_drive_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.9/5.0
Behavior3/5

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

The description explicitly states the operation does not execute the notebook, which is a key behavioral trait. However, with no annotations provided, it fails to disclose other aspects like permission requirements or side effects on the original file.

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?

The description is a single, front-loaded sentence that efficiently conveys the core action and a key constraint. Every word is necessary.

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

Completeness3/5

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

For a simple copy tool with only two parameters, the description provides the essential action. However, it lacks details on return values (no output schema) and does not integrate with sibling tools to indicate when copying is preferable over other operations.

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?

The input schema has 0% description coverage, and the description does not explain the purpose of the two parameters (file_id and name). This leaves the agent unclear on what values to provide.

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?

The description clearly states it copies a notebook file in Google Drive and adds the nuance that it does so without executing it. This specifies the verb and resource, but does not differentiate from siblings like pull_drive_notebook or push_local_notebook, which have distinct purposes.

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 is provided on when to use this tool versus alternatives such as pull_drive_notebook or push_local_notebook. There is no mention of prerequisites or exclusion criteria.

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