Skip to main content
Glama
Sign In
tmux-mcp

tmux-mcp

by fr1sk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

split_pane

Split a tmux pane horizontally or vertically. Specify target, direction, size, command, and working directory to create new panes.

Instructions

Split a tmux pane horizontally or vertically. 'horizontal' = left/right panes side by side. 'vertical' = top/bottom panes stacked. Target format: 'session:window.pane' or 'session:window'.

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": {
      "target": "<target>"
    },
    "name": "split_pane"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for the new pane.
sizeNoSize of the new pane as a percentage (e.g. 50).
targetYesTarget pane or window to split: 'session:window.pane'
commandNoShell command to run in the new pane. WARNING: executes in your shell.
directionNo'horizontal' splits left/right, 'vertical' splits top/bottom (default: horizontal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.8/5.0
Behavior3/5

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

Discloses that command executes in shell (warning) and direction defaults, but lacks details on side effects, undoability, or permissions needed. Relies on description alone since no annotations.

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?

Three concise sentences, front-loaded with action and critical details. No wasted words.

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

Completeness4/5

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

Covers all parameters indirectly, explains direction and target format. Lacks output/return value description, but adequate for a simple tool without output schema.

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?

Adds meaning beyond schema by clarifying target format ('session:window.pane') and direction descriptions ('left/right side by side', 'top/bottom stacked'). Schema coverage is 100%, but description enhances usability.

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?

Clearly states the tool splits a tmux pane, specifies horizontal vs vertical, and explains target format. Differentiates from sibling tools like new_window or kill_pane.

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?

No explicit guidance on when to use vs alternatives (e.g., new_window). Only implies usage for splitting panes, with no when-not-to-use or prerequisite conditions.

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