Skip to main content
Glama
Liu-Eroteme
by Liu-Eroteme

run

Execute notebook cells with automatic dependency re-execution, handle timeouts, and receive condensed outputs including images.

Instructions

Execute cells on the notebook's persistent kernel.

Default (no `cells`): every stale cell in document order — minimal
recompute after edits. With `cells`: exactly those cells, even if fresh
(API calls, randomness), preceded by their stale ancestors so inputs are
trustworthy (`fresh_deps=false` skips the ancestor pass). Outputs are
persisted and returned condensed; charts come back as images; `quiet`
collapses ok cells to status lines. If everything finishes within
`wait_seconds` you get full results; otherwise execution continues in the
background — watch it via notebook_overview / read_cells (live output),
stop it via interrupt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
cellsNo
quietNo
fresh_depsNo
wait_secondsNo
timeout_secondsNo
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: outputs persisted, charts as images, background continuation on timeout, and the effect of fresh_deps on cell dependencies. No hidden side effects.

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 paragraph that front-loads the main action. It is detailed but not overly verbose; every sentence contributes. However, it could benefit from bullet points for readability.

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?

For a complex tool with 6 parameters, no output schema, and no annotations, the description covers all key behaviors, edge cases (background execution, fresh ancenstors), and references monitoring/interrupt tools, making it self-sufficient.

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?

With 0% schema description coverage, the description adds significant meaning for cells, quiet, fresh_deps, and wait_seconds. However, timeout_seconds is not explained, and path is not described (though self-explanatory).

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's purpose: 'Execute cells on the notebook's persistent kernel.' It distinguishes default behavior (stale cells) from explicit cell execution, and contrasts with sibling tools like interrupt, read_cells, and notebook_overview.

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?

Provides explicit guidance: default for minimal recompute, with cells for specific execution, fresh_deps to control ancestor pass, quiet to collapse outputs, and background behavior with wait_seconds. References sibling tools for monitoring and stopping.

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/Liu-Eroteme/jupyter_mcp'

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