Skip to main content
Glama
Sign In
jupyter-notebook-mcp

jupyter-notebook-mcp

by g0g5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_cell

Delete a cell by index from the active Jupyter notebook and return previews of affected neighboring cells.

Instructions

Remove a cell and return previews of affected neighboring cells.

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

Input Schema

NameRequiredDescriptionDefault
indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 states that a cell is removed and neighboring previews are returned, but it does not disclose whether removal is permanent, what permissions are required, what happens on invalid index, or any other behavioral trait beyond the obvious mutation.

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?

A single front-loaded sentence with no wasted words. It is appropriately sized for a simple tool, though its terseness contributes to gaps in other dimensions rather than being a structure problem.

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 annotations, a required index parameter with no schema description, and an ambiguous sibling delete_cell, the description is not complete enough to call the tool correctly. It mentions returned previews (and an output schema exists), but omits essential parameter semantics and selection guidance.

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?

Schema description coverage is 0%, so the description must compensate for the single parameter. It never mentions the index parameter, its meaning, range, or base (e.g., 0-based position). The description adds no parameter semantics beyond the schema's bare integer type.

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?

States a specific verb and resource: "Remove a cell." It also adds a return side effect (previews of neighboring cells). However, it does not distinguish itself from the sibling tool delete_cell, so an agent cannot tell which removal tool to choose without opening schemas.

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?

Provides no when-to-use guidance, no prerequisites, and no alternatives. With a sibling named delete_cell, the lack of differentiation is especially problematic. The description merely restates the action.

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