Skip to main content
Glama
Sign In
jupyter-notebook-mcp

jupyter-notebook-mcp

by g0g5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

from_markdown

Load Markdown notebook blocks from disk and replace active Jupyter cells to update the current notebook session.

Instructions

Load markdown notebook blocks from disk and replace active cells.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/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, but it does disclose one important behavioral fact: the operation replaces active cells, i.e. it is destructive to current in-memory state. It omits prerequisites (must a notebook already be open?), reversibility, and what happens to unsaved changes.

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?

A single efficient sentence that front-loads the verb and resource and packs the side effect into the same clause. No padding, though it is arguably too terse for the behaviors it hides.

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 this is a mutation tool with no annotations and an undocumented path parameter. The description should clarify prerequisites and the interaction with the other notebook/cell siblings; as written it leaves too much for the agent to infer.

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% for the single 'path' parameter, so the description must compensate and does not. 'From disk' loosely implies a filesystem path but gives no format, extension, or whether it is relative to a workspace root.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb (Load) and a resource (markdown notebook blocks) plus the side effect (replace active cells). However 'notebook blocks' is jargon-y and it doesn't distinguish itself from load_notebook, which an agent would reasonably pick as the more obvious sibling for loading a notebook.

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?

There is no when-to-use guidance and no alternative named. An agent cannot tell from the text whether this is preferred over load_notebook, or when a markdown-source load is appropriate versus reading individual cells with read_cell.

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