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

colab-drive-mcp

by YummyTastyCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

push_local_notebook

Upload a local .ipynb file to Google Drive without executing it. Synchronizes your local notebook to Drive for later use.

Instructions

Synchronize a local notebook file to 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": {
      "local_path": "<local_path>"
    },
    "name": "push_local_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
local_pathYes
drive_nameNo
file_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'without executing it' but fails to disclose key behaviors such as overwrite policy, effect on existing Drive files, authentication requirements, or whether local files are modified. For a mutation tool with no annotations, this is insufficient.

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?

The description is a single short sentence with no fluff. It could be more informative without becoming verbose, but it is efficiently concise.

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 the tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It does not cover return behavior, error conditions, or parameter dependencies. For a sync operation, important details like conflict resolution or confirmation prompts are missing.

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%, meaning the parameter names and types in the schema provide no descriptions. The tool description adds no explanation for local_path, drive_name, or file_id. It only implies the drive name via context, but does not specify format, defaults, or optionality. This is a critical gap.

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 the tool synchronizes a local notebook to Drive, specifying it does not execute the notebook. This verb+resource combination is specific and helps distinguish from siblings like pull_drive_notebook. However, 'Synchronize' could be ambiguous (push vs. two-way), so not a perfect 5.

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 explicit guidance on when to use this tool versus alternatives such as pull_drive_notebook or get_notebook_sync_status. There is no mention of prerequisites, context, or exclusions.

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