Skip to main content
Glama

jupyter_insert_cell

Insert a new code or markdown cell at a specific position in a Jupyter notebook, enabling precise control over notebook structure and content.

Instructions

Insert a new cell at a specific position in the notebook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notebook_pathYesPath to the notebook
cell_indexYesPosition to insert (0-based, cells after this shift down)
sourceYesCell content (code or markdown)
cell_typeNoType of cell - 'code' or 'markdown' (default: code)code

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 the full burden. It omits behavioral details such as that subsequent cells shift down (implied only in the schema parameter description). The description should explicitly state side effects like cell renumbering.

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?

The description is a single, well-structured sentence that immediately conveys the core action. It is front-loaded and contains no redundant or superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description need not detail return values. However, it could briefly mention cell shifting behavior for completeness. Overall, it is adequate for a relatively simple insertion operation.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions. It does not clarify parameter purpose or constraints beyond what the schema already provides.

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 clearly states 'Insert a new cell at a specific position', which distinguishes it from the sibling 'jupyter_append_cell' that adds at the end. The verb 'Insert' and the resource 'new cell' are specific and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like 'jupyter_append_cell' or 'jupyter_update_cell'. It does not mention scenarios, prerequisites, or when not to use it.

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/xLydianSoftware/aix'

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