Skip to main content
Glama
Sign In
jupyter_mcp

jupyter_mcp

by Liu-Eroteme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

undo_last

Revert the last change made to a Jupyter notebook, restoring its previous state.

Instructions

Restore the notebook to its state before the most recent mutation.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so description must fully disclose behavior. It discloses the core action but does not mention effects when no prior mutations exist, idempotency, or any destructive side effects. Minimal transparency.

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?

Single sentence, no waste. However, it could include more detail without losing conciseness. Still, it is efficient and directly states the tool's function.

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?

Given the lack of annotations and parameter documentation, the description does not provide sufficient context for safe usage. No mention of return values from output schema, prerequisites, or edge cases.

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 fails to explain the required 'path' parameter. The user is left to infer that path refers to the notebook, but no explicit meaning or constraints are provided.

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?

Description states 'Restore the notebook to its state before the most recent mutation.' This is a specific verb (restore) and resource (notebook state) with clear scope. It distinguishes itself from sibling tools like add_cell or remove_cell which are mutations.

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

Usage Guidelines3/5

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

Implies usage for reverting the last mutation, but does not explicitly state when to use or provide alternatives. Given the tool name and context, it's adequately implied but lacks explicit guidance.

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