Skip to main content
Glama
Sign In
jupyter-notebook-mcp

jupyter-notebook-mcp

by g0g5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_notebook

Validate and save the active Jupyter notebook to its current or new path. Ensures data integrity before saving to prevent loss.

Instructions

Validate and save the active notebook to current or new path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
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 behavioral disclosure. 'Validate' hints that a validation step occurs but never says what is validated, what happens on failure, whether an existing file at 'path' is overwritten, or what permissions are needed for a mutation of this kind.

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; the operation and its target path behavior come first. It is arguably terse to the point of under-specification, but nothing in it is wasted.

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-value explanation is not required. But for a save/mutation tool with zero annotations, the description should disclose overwrite and validation-failure behavior, and it does not; sibling differentiation is also absent.

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 0% and the sole parameter is undocumented in the schema, so the burden falls on the description. 'To current or new path' usefully clarifies the null-vs-provided convention (default null means save in place), but no format, file extension, or conflict behavior is specified, so it only partially compensates.

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?

States a specific verb pair ('validate and save') and a specific resource ('the active notebook'), so the agent knows exactly what operation is performed. However, it never names or distinguishes itself from the closest sibling, save_markdown, leaving the notebook-vs-markdown distinction to inference.

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 save_markdown or the write-oriented cell tools, and no prerequisites or preconditions are given. The only usable signal is the tool name itself, which is implicit at best.

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