hyperpanes-mcp

Overview Schema Source Related Servers Discussions Admin

Move pane

move_pane

Move a live terminal pane to another tab or window without restarting it, preserving its session, pty, label, and metadata; specify an existing tab, new tab, or project.

Instructions

Move a LIVE pane to another tab, in the same window or another one, without restarting it: the pty, session, paneId, label, subtitle, meta and inbox are untouched; only its tab changes. Give exactly one target: tabId (an existing tab, as list_panes reports it), newTab ({title?, color?}: a new background tab), or project (a remembered project id, name or absolute path: that project's tab in the window, reused if present, else created with the project's name and colour). windowId picks the window for newTab/project (default: the pane's own). Returns the target tabId. A tab emptied by the move closes; the window's only pane cannot move (409). Needs a hyperpanes app with the movePane command.

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": {
      "paneId": "<paneId>"
    },
    "name": "move_pane"
  }
}

Input Schema

Name	Required	Description
`tabId`	No	an existing tab to move into
`newTab`	No	move into a brand-new tab (opened in the background)
`paneId`	Yes
`project`	No	move into the project's tab (id, name or absolute path; see list_projects)
`windowId`	No	window for newTab/project (default: the pane's own)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.25Nov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses what is preserved (pty, session, paneId, label, subtitle, meta, inbox), that only the tab changes, that an emptied tab closes, the 409 failure for a window's only pane, the return value, and a runtime prerequisite (hyperpanes app with the movePane command).

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?

Front-loaded with the core action and preservation guarantee, and every sentence contributes operational detail. It is dense and parenthetical-heavy, which slightly hurts scanability, but nothing is redundant filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with no annotations and no output schema, yet the description covers the return value, the partial-failure case (409), the side effect (tab closing), target exclusivity, and the app prerequisite. An agent could invoke this correctly without consulting anything else.

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

Parameters4/5

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

Schema coverage is already 80%, so the baseline is 3; the description adds genuine meaning on top by clarifying that tabId must come from list_panes, that newTab opens in the background, and that project reuse-or-creates a tab using the project's name and colour. Only the newTab title/color field details and the paneId requirement are left to the schema.

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 and resource ('Move a LIVE pane to another tab') and immediately bounds scope: same window or another, no restart, pty/session/metadata untouched. This is clearly distinct from siblings such as open_pane, restart_pane or close_pane, which an agent could otherwise confuse with moving.

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?

Explicitly enforces the selection rule 'give exactly one target' and then explains each of the three mutually exclusive options (tabId, newTab, project), including windowId's default. It stops short of naming sibling alternatives to avoid (e.g. open_pane for a fresh pane, restart_pane for a reload), so the exclusions are implied rather than stated.

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