Skip to main content
Glama
qtalen

jupyter-kernel-mcp

by qtalen

delete_cell

Remove a Jupyter notebook cell at a specified index to clean up or reorganize content.

Instructions

Delete a cell by index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cell_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. The description confirms a destructive operation but fails to specify effects on other cells (e.g., re-indexing), reversibility, or error conditions (e.g., index out of bounds).

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 sentence, front-loading the core purpose. It is concise but omits necessary details such as context (notebook) and error handling, making it slightly under-specified for a production tool.

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?

Although an output schema exists (reducing need for return value explanation), the description lacks completeness regarding prerequisites (e.g., notebook must be open via use_notebook) and edge cases (e.g., deleting the last cell). This limits an AI agent's ability to invoke the tool correctly in all scenarios.

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?

The single parameter cell_index lacks schema description coverage (0%). The description adds minimal meaning—'by index'—but does not specify indexing base (0- or 1-based), valid range, or behavior for invalid values. This is insufficient for correct invocation.

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?

The description 'Delete a cell by index' clearly states the action (delete), the resource (a cell), and the method (by index). It unambiguously distinguishes this tool from siblings like insert_cell or edit_cell_source, which perform different operations on cells.

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 is provided on when to use this tool versus alternatives (e.g., clearing a cell's content instead of deleting it). There is no mention of prerequisites, such as the need for an active notebook, or any conditions under which deletion is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qtalen/jupyter-kernel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server