Skip to main content
Glama
Sign In
ipynb-mcp

ipynb-mcp

by YmSaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restart_kernel

Restart a notebook's kernel to clear all in-memory variables and fix stalled or inconsistent execution states.

Instructions

Restart the notebook's kernel, clearing all in-memory variables.

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": "restart_kernel"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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. It explicitly discloses the key destructive side effect: clearing all in-memory variables. It does not mention potential interruption of running code, but the main behavioral trait is stated.

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?

One short sentence communicates the action and outcome immediately with no filler. Every word earns its place.

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?

The required 'path' parameter is completely undocumented, which is a significant gap for a tool with only one parameter. The description also provides no prerequisites or exclusions, leaving the tool under-specified despite its apparent simplicity.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the required 'path' parameter at all. An agent cannot tell whether 'path' refers to the notebook path, kernel identifier, or server endpoint.

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?

States a specific verb ('Restart') on a specific resource ('the notebook's kernel') and names the consequence ('clearing all in-memory variables'). This clearly distinguishes it from sibling tools that operate on cells.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the appropriate use case: reset the kernel state when in-memory variables need clearing. It does not explicitly mention when not to use it or name alternatives, but the context is clear enough given the sibling set.

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