Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IPYNB_ROOTNoRoot directory fence. The server fences all paths to this directory. Defaults to the process working directory.
IPYNB_IMAGESNoImage block policy (auto: images only on full-output reads and runs). Default is auto.auto
IPYNB_PYTHONNoExplicit interpreter (failure is final). Default is auto.auto
IPYNB_LOG_LEVELNostderr log level. Default is info.info
IPYNB_READ_ONLYNoOnly notebook_read and kernel status allowed. Default is false.false
IPYNB_BACKUP_KEEPNoRolling backups per notebook. Default is 10.10
IPYNB_ARTIFACT_DIRNoWhere image artifacts are written. Default is platform cache.
IPYNB_PREVIEW_LINESNoSource preview lines. Default is 12.12
IPYNB_MAX_IMAGE_BYTESNoMax bytes per image. Default is 20971520.20971520
IPYNB_INLINE_TEXT_CHARSNoText output truncation threshold. Default is 20000.20000
IPYNB_ALLOW_OUTSIDE_ROOTNoAllow paths outside the root. Default is false.false
IPYNB_KERNEL_IDLE_SECONDSNoIdle kernel reclamation. Default is 3600.3600
IPYNB_MAX_IMAGES_PER_CALLNoImage blocks per tool call. Default is 20.20
IPYNB_EXEC_TIMEOUT_SECONDSNoPer-cell timeout. Default is 300.300
IPYNB_BACKGROUND_THRESHOLD_SECONDSNoRuns whose estimated upper bound (timeout_seconds × target cells) exceeds 10× this go background. Default is 30.30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
notebook_readA

Read a Jupyter notebook: cell index, type, source and existing outputs. Set include_outputs='full' to get a cell's outputs including images.

notebook_editB

Edit notebook cells. Every source change requires a compare-and-swap anchor (expected_source_hash or expected_text); a mismatch fails the whole request without writing.

notebook_runA

Execute notebook cells. mode='resume' runs only the target cells in the live kernel; 'replay' silently rebuilds state from cell 0 first; 'full' re-runs everything.

notebook_run_statusA

Poll a background notebook run started by notebook_run.

notebook_run_cancelB

Cancel a background notebook run started by notebook_run.

notebook_kernelC

Inspect or manage the kernels held for notebooks: status, start, shutdown, restart.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a clearly distinct action on a notebook: read, edit, run, poll run status, cancel run, and manage kernels. The run_status/run_cancel pair are explicitly scoped to background runs started by notebook_run, so there is no real misselection risk.

Naming Consistency5/5

All six tools use a uniform snake_case notebook_* prefix with a predictable verb/noun suffix (read, edit, run, run_status, run_cancel, kernel). The pattern is consistent throughout with no style deviations.

Tool Count5/5

Six tools is well-scoped for a notebook server, covering the core read/edit/execute workflow plus async run lifecycle and kernel management. No tool feels redundant or padded.

Completeness4/5

Read, edit, run, and kernel lifecycle are covered, including async run polling and cancellation. Minor gaps remain, such as creating a brand-new notebook file or deleting cells/notebooks explicitly, but these are largely workable via edit.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive