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

colab-drive-mcp

by YummyTastyCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_local_cell

Remove a notebook cell from a local .ipynb file by providing the file path and cell index.

Instructions

Delete a cell from a 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>",
      "index": "<index>"
    },
    "name": "delete_local_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
indexYes

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. The description only states 'delete', implying a destructive action, but lacks detail on irreversibility, impact on notebook state, or whether it affects other cells. Beyond the obvious, no behavioral traits are disclosed.

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

Conciseness3/5

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

The description is a single sentence, concise and front-loaded. However, it is under-specified; while concise, it sacrifices informativeness.

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 no output schema, no annotations, and simple parameters, the description is minimal. It does not explain the effect on the notebook (e.g., shifting indices), return values, or error conditions, which an agent needs to invoke correctly.

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%, so the description must explain parameters. It does not explain 'path' (notebook file path?) or 'index' (position of cell?), leaving the agent to infer. This is insufficient.

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 verb 'Delete' and the resource 'a cell from a local notebook'. It distinguishes from siblings like 'add_local_cell' and 'update_local_cell' by specifying deletion, but does not explicitly differentiate its scope.

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. No context about prerequisites, such as requiring the notebook to exist, or when not to use it (e.g., if a cell is critical).

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