Delete a single cell by its numeric index from a Colab or Jupyter notebook to remove unwanted code or markdown blocks.
Delete one cell by index.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| index | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It only restates the name and adds the index mechanism. It does not mention whether deletion is permanent, what happens if the index is out of bounds, whether the operation requires write permissions, or any side effects on the notebook. The destructive nature is implied but not elaborated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one short sentence that gets straight to the point. It contains no filler and is easy to parse, though it may be too terse to be fully informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two required parameters and no annotations or output schema, the description is incomplete: it fails to define what 'path' refers to, does not mention error handling, and does not clarify the scope of deletion. An agent would need to infer path semantics from the parameter name alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It clarifies that 'index' is the cell index, but it does not explain 'path' (presumably the notebook path) or any constraints. The description adds minimal value over the raw schema property names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Delete') and resource ('cell') and identifies the selection mechanism ('by index'). It clearly distinguishes from sibling tools like colab_add_cell, colab_edit_cell, and colab_execute_cell.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool over alternatives, no prerequisites (e.g., notebook must exist), and no conditions under which deletion is appropriate. It simply states the action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.