Skip to main content
Glama
Sign In
Jupyter Notebook MCP Server

Jupyter Notebook MCP Server

by shwetalsoni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

execute_entire_notebook

Execute all code cells in a Jupyter notebook sequentially, with configurable timeout, kernel, and stop-on-error. Returns an execution summary.

Instructions

Execute all code cells in a Jupyter notebook sequentially.

Args:
    notebook_path: Absolute path to the .ipynb file
    kernel_name: Jupyter kernel to use for execution
    timeout_per_cell: Timeout per cell in seconds
    stop_on_error: Whether to stop execution if a cell fails

Returns:
    Execution summary with results for each cell

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": {
      "notebook_path": "<notebook_path>"
    },
    "name": "execute_entire_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
kernel_nameNopython3
notebook_pathYes
stop_on_errorNo
timeout_per_cellNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes sequential execution and the stop_on_error parameter, but does not disclose potential side effects (e.g., modifying the notebook, resource consumption) or details on how execution affects the notebook state.

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 concise, using a clear first sentence for purpose followed by structured Args and Returns sections. Every sentence adds value without redundancy.

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

Completeness4/5

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

Given the complexity (4 parameters, no output schema, no annotations), the description covers the tool's purpose and parameters adequately. It mentions a return summary, though details on the summary format are minimal. Still, it provides enough context for basic usage.

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

Parameters4/5

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

Schema description coverage is 0%, but the description's Args section explains each parameter's meaning (absolute path, Jupyter kernel, timeout in seconds, boolean for stop). This adds value beyond the raw schema, though parameter descriptions could be more detailed.

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 'Execute all code cells in a Jupyter notebook sequentially,' specifying the verb (execute), resource (notebook), and scope (all cells). This distinguishes it from siblings like execute_notebook_cell or add_cell_to_notebook.

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 explicit guidance on when to use this tool versus alternatives. It does not mention situations to prefer execute_notebook_cell or other siblings, nor does it provide exclusions or prerequisites.

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