Skip to main content
Glama
Sign In
jupyter_mcp

jupyter_mcp

by Liu-Eroteme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_cell

Move a notebook cell to a specified index or after an existing cell to reorganize content.

Instructions

Move a cell: after an existing cell ('' moves to top) or to index.

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": "<name>",
      "expected_rev": "<expected_rev>"
    },
    "name": "move_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYes
afterNo
indexNo
expected_revYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/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 only discloses the two positioning options (after, index) but fails to mention side effects, prerequisites, or mutation behavior (e.g., does it require kernel, affect other cells?). The note about empty string for after moving to top is helpful but insufficient.

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?

The description is a single sentence with no fluff, front-loaded with the verb 'Move'. Every word earns its place, making it highly efficient.

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 5 parameters (3 required), no annotations, and no schema descriptions, the description is incomplete. It does not explain the required parameters (name, path, expected_rev) or the output schema, leaving the agent with significant unknowns for correct invocation.

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

Parameters3/5

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

With schema description coverage at 0%, the description adds meaning for the 'after' and 'index' parameters (e.g., '' moves to top), but ignores the required parameters 'name', 'path', and 'expected_rev', which remain unexplained. It partially compensates but leaves gaps.

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?

The description clearly states the verb 'Move' and the resource 'cell', and specifies two distinct ways to specify destination ('after' an existing cell or to an 'index'), which clearly distinguishes this tool from sibling tools like add_cell, remove_cell, or update_cell.

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?

The description implies usage for reordering cells but does not explicitly state when to use this tool versus alternatives like add_cell or update_cell, nor does it provide exclusions or context for when not to use it.

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