Skip to main content
Glama
azharlabs
by azharlabs

insert_cell

Add a new code, markdown, or raw cell at a specified position in a Jupyter notebook to organize content and structure.

Instructions

Insert a new cell at a specific position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notebook_pathYesAbsolute path to the Jupyter notebook file
positionYesPosition to insert the cell (0-based)
cell_typeNoType of cell to createcode
sourceNoInitial source code/content for the cell

Implementation Reference

  • The core handler function that implements the insert_cell tool logic: reads notebook, validates position and cell type, formats source, creates and inserts new cell, writes notebook, returns success message.
    async insertCell(notebookPath, position, cellType = 'code', source = '') {
      const notebook = await this.readNotebook(notebookPath);
      this.validateCellType(cellType);
      
      if (position < 0 || position > notebook.cells.length) {
        throw new Error(`Invalid position ${position}. Must be between 0 and ${notebook.cells.length}`);
      }
      
      // Convert string to array format - each line should end with \n except the last
      let sourceArray;
      if (!source) {
        sourceArray = [''];
      } else {
        const lines = source.split('\n');
        sourceArray = lines.map((line, index) => {
          if (index === lines.length - 1) {
            return line === '' ? '' : line;
          } else {
            return line + '\n';
          }
        });
        
        // Remove empty last element if original ended with \n
        if (sourceArray.length > 1 && sourceArray[sourceArray.length - 1] === '') {
          sourceArray.pop();
        }
      }
      
      const newCell = {
        cell_type: cellType,
        metadata: {},
        source: sourceArray
      };
      
      if (cellType === 'code') {
        newCell.execution_count = null;
        newCell.outputs = [];
      }
      
      notebook.cells.splice(position, 0, newCell);
      await this.writeNotebook(notebookPath, notebook);
      
      return {
        content: [
          {
            type: "text",
            text: `Successfully inserted ${cellType} cell at position ${position}`
          }
        ]
      };
    }
  • Input schema for the insert_cell tool defining parameters: notebook_path (required), position (required), cell_type (optional, default 'code'), source (optional, default '').
    {
      name: "insert_cell",
      description: "Insert a new cell at a specific position",
      inputSchema: {
        type: "object",
        properties: {
          notebook_path: {
            type: "string",
            description: "Absolute path to the Jupyter notebook file"
          },
          position: {
            type: "integer",
            description: "Position to insert the cell (0-based)"
          },
          cell_type: {
            type: "string",
            enum: ["code", "markdown", "raw"],
            default: "code",
            description: "Type of cell to create"
          },
          source: {
            type: "string",
            default: "",
            description: "Initial source code/content for the cell"
          }
        },
        required: ["notebook_path", "position"]
      }
    },
  • src/index.js:344-350 (registration)
    Registration in the CallToolRequestSchema handler switch statement that dispatches 'insert_cell' calls to jupyterHandler.insertCell with argument handling.
    case "insert_cell":
      return await this.jupyterHandler.insertCell(
        args.notebook_path,
        args.position,
        args.cell_type || "code",
        args.source || ""
      );
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action without disclosing behavioral traits like permissions needed, whether it modifies the file in place, error handling, or effects on existing cells. It's minimal and lacks crucial context for a mutation tool.

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, efficient sentence that is front-loaded with the core purpose. There is no wasted wording, making it highly concise and well-structured.

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 the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It fails to address key aspects like what the tool returns, error conditions, or how it interacts with the notebook file, leaving significant gaps for an agent.

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 description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema, such as examples or edge cases, meeting the baseline for high coverage.

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?

The description clearly states the action ('insert') and resource ('a new cell') with specificity about the location ('at a specific position'). It distinguishes from siblings like 'add_cell' by emphasizing positional insertion, though it doesn't explicitly compare to all alternatives.

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 like 'add_cell' or 'bulk_edit_cells'. The description implies usage for inserting a single cell at a position but lacks explicit context or exclusions.

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/azharlabs/mcp-jupyter-server'

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