Skip to main content
Glama

notebook_create

Create a new empty notebook at a specified runtime path to start GPU-backed machine-learning work.

Instructions

Create a new empty notebook at path on the runtime.

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": {
      "path": "<path>"
    },
    "name": "notebook_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say what happens if the path already exists (error vs overwrite), whether the notebook is persisted or ephemeral, or what permissions/state are required. "Empty" and "on the runtime" are the only behavioral facts disclosed.

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?

One short sentence with the action and target front-loaded and zero filler. Its brevity is efficient rather than padded, though it leaves too much unsaid for a mutation tool.

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

Completeness2/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 values need not be explained, but for a creation/mutation tool with no annotations and an undocumented parameter, the definition omits prerequisites, collision behavior, and path format. An agent could not reliably call this correctly without guessing.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain the single `path` parameter, yet it only echoes the name. It adds that the path is "on the runtime" but gives no format expectations (absolute vs relative, directory vs file, whether a .ipynb extension is required or appended).

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?

Specific verb+resource ("Create a new empty notebook") with the target location named, which cleanly separates it from the sibling cell-editing and read tools. It does not explicitly name an alternative, but the create/empty framing is unambiguous.

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 guidance on when to create a notebook versus using notebook_add_cell on an existing one, and no stated prerequisites such as whether a runtime must be started or connected first. The phrase "on the runtime" hints at a precondition without confirming it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.