Skip to main content
Glama
mstampfer

Claude Code Notebook MCP

by mstampfer

notebook_edit_cell

Replace the source code of a specific cell in a Jupyter notebook by providing the notebook path, cell index, and new source content.

Instructions

Replaces the source content of a specific cell

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the notebook
cell_indexYesIndex of the cell to edit
new_sourceYesNew source content for the cell
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 of disclosing behavior. It states 'replaces', implying destructive overwrite, but fails to specify whether the entire cell source is replaced, if there are side effects (e.g., cell execution state), or if any validation occurs. More detail is needed 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that immediately conveys the action. It is concise with no wasted words. However, it could include a bit more context without losing conciseness.

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?

The description does not explain the return value, whether the cell retains its type or other metadata after editing, or if any validation is performed. Given the number of sibling tools, more context is needed to ensure an agent can use this tool correctly without guessing about side effects or outcomes.

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%, with all three parameters (path, cell_index, new_source) already described in the schema. The tool description adds no additional semantic information beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'Replaces the source content of a specific cell' clearly states the verb and resource, distinguishing it from sibling tools like notebook_add_cell (adds a new cell) and notebook_edit_cell_metadata (edits only metadata). However, it doesn't explicitly emphasize that it replaces the entire source content, not just appends or modifies.

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 on when to use this tool versus alternatives like notebook_edit_cell_metadata or notebook_edit_cell_output. There is no mention of when-not to use it or any prerequisites (e.g., cell must exist).

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/mstampfer/claude-code-notebook-mcp'

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