Skip to main content
Glama
Sign In
jupyter_mcp

jupyter_mcp

by Liu-Eroteme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_cell

Delete a notebook cell by specifying its path and name. Requires the current revision to confirm deletion; supports undo with the undo_last tool.

Instructions

Delete a cell (requires its current rev; undo with undo_last).

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": "<name>",
      "expected_rev": "<expected_rev>"
    },
    "name": "remove_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYes
expected_revYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that deletion depends on a revision and can be undone. With no annotations, this covers key behavioral traits. Could mention what happens on invalid rev or full side effects.

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?

One sentence, no fluff. Every word earns its place. Information is front-loaded (action first, then requirements).

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?

Covers core behavior and a key constraint, but lacks explanation of 'name' and 'path' parameters, return value (output schema exists), and error scenarios. Brief but leaves gaps for a 3-param tool.

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

Parameters2/5

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

Only 'expected_rev' is hinted at via 'current rev'; 'name' and 'path' are not described. Schema coverage is 0%, and the description does little to explain these parameters' meaning or format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Delete a cell' – a specific verb and resource. Distinguishes from sibling tools like add_cell, update_cell, move_cell.

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

Usage Guidelines5/5

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

Explicitly mentions prerequisite ('requires its current rev') and provides alternative/recovery via 'undo with undo_last'. Provides clear guidance on when and how to use.

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