Skip to main content
Glama
Sign In
ipynb-mcp

ipynb-mcp

by YmSaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

edit_cell

Replace a notebook cell's source code, markdown, or raw content, and optionally change its type to code, markdown, or raw.

Instructions

Replace a cell's source and optionally its type.

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": "edit_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
indexYes
sourceYes
cell_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of describing behavior. It communicates that source and optionally type are overwritten, but it does not disclose side effects such as whether execution state or outputs are affected, whether changes persist, or what happens if an invalid type is supplied.

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, front-loaded sentence with no filler or repetition. Every one of its eight words adds information.

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?

Despite a schema with types, enums, and defaults, the total definition is thin for a mutating tool with zero annotations: the path/index semantics and usage conditions are left implicit, and no behavioral context is added beyond the core action.

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. It adds meaning for 'source' and 'cell_type' but leaves 'path' and 'index' entirely unexplained, and it never states how the target cell is identified.

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 states a specific verb/resource pair: 'Replace a cell's source and optionally its type.' This clearly differentiates edit_cell from siblings like add_cell, read_cell, and run_cell.

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 guidance about when to use edit_cell rather than add_cell, read_cell, or run_cell, nor any stated prerequisites. The intended usage is only implied by the verb 'Replace'.

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

Deploy Server

Other Tools