Skip to main content
Glama

notebook_edit_cell

Replace the source of a notebook cell by index to update code or fix errors without rewriting the full notebook.

Instructions

Replace the source of cell index in a notebook.

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>",
      "index": "<index>",
      "source": "<source>"
    },
    "name": "notebook_edit_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
indexYes
sourceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little. It implies a destructive overwrite of existing source, but says nothing about what happens on an out-of-range index, whether the cell's outputs or execution state are cleared, or whether any auth/permission is required.

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 filler or redundancy. It is efficiently written, though its brevity reflects under-specification rather than disciplined economy.

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?

An output schema exists, so return values need not be explained, and the tool's operation is simple (three flat required params). However, for a mutation tool with zero annotation coverage and zero parameter documentation, the description leaves too much for an agent to infer.

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, and it does not. It names 'index' and 'source' but adds no meaning — not whether the index is 0- or 1-based, whether source replaces the entire cell body, and it never mentions the required 'path' parameter at all.

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 uses a specific verb ('Replace') on a specific resource ('the source of cell index in a notebook'), which clearly separates it from notebook_add_cell and notebook_delete_cell. It stops short of explicitly naming those siblings, but the operation is 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?

There is no statement of when to use this tool versus notebook_add_cell, notebook_delete_cell, or notebook_run_cell. The verb 'Replace' hints that it modifies existing content rather than creating it, but no prerequisites (e.g. the cell must already exist, a runtime need not be connected) or exclusions are given.

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