Skip to main content
Glama
tmlksu

notebook-edit

by tmlksu

create_notebook

Create a new .ipynb notebook file at a specified path, optionally with initial code, markdown, or raw cells. Avoids overwriting existing files and requires parent directory to exist.

Instructions

Create a NEW empty .ipynb notebook at path (optionally with initial cells).

Use this instead of hand-writing notebook JSON. cells (optional) is a list of {cell_type, source, summary?} — the same shape as insert_cells — seeded in order; omit it for an empty notebook. Refuses to overwrite an existing file and requires the parent directory to exist (both error). The notebook is nbformat 4.5, so every created cell gets a stable id right away. Returns {"path", "num_cells", "ids"}. cell_type must be one of: code, markdown, raw.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
cellsNo
Behavior5/5

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

Describes behavioral traits beyond annotations: refuses overwrite, requires parent dir, nbformat 4.5, stable cell IDs, return fields, cell_type constraint. No annotations exist, so full burden is carried.

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?

Concise yet comprehensive. Uses parentheses and quotes for clarity. Front-loaded with main action, every sentence adds value.

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

Completeness5/5

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

Complete for a 2-parameter tool with no output schema. Covers constraints, return value, related tools, and format details.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining path (required) and cells (optional shape, cell_type constraint) beyond the bare schema.

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 the tool creates a new .ipynb notebook at a given path, optionally with initial cells. It distinguishes from sibling tools by saying 'Use this instead of hand-writing notebook JSON.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use (creating new notebooks) and when not to (refuses to overwrite, parent dir required). Mentions alternatives like insert_cells for seeding cells.

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/tmlksu/nbedit-mcp'

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