tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

Python

Local

select_pane

Select the active tmux pane by its ID or direction (L, R, U, D) for precise and efficient pane navigation.

Instructions

Select active pane by ID or direction (L, R, U, D)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "select_pane"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No
`direction`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare the tool is not read-only and not idempotent, which covers its mutating nature. The description adds that it changes the active pane, but it does not disclose potential side effects, error behavior, or what happens if both target and direction are provided. This is acceptable given the annotation coverage but not richly detailed.

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, front-loaded sentence with no redundancy. Every word contributes to understanding the tool's purpose and parameter semantics.

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?

The tool has an output schema and annotations that cover return values and mutability. The description gives the essential action and parameter semantics. It is complete enough for a simple selection tool, though it leaves ambiguity about combined or invalid inputs.

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?

With 0% schema description coverage, the description compensates by mapping target to an ID and direction to L/R/U/D. This adds meaning beyond the bare schema names. However, it does not explain the ID format, whether parameters are mutually exclusive, or the default behavior when neither is 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?

The description clearly states the action ('Select'), the target resource ('active pane'), and the two methods ('by ID or direction'). It explicitly lists the direction values (L, R, U, D), making it easy to distinguish from sibling tools like list_panes or select_window.

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 when you want to change the active pane, but it does not provide explicit when-to-use guidance or mention alternatives. The 'by ID or direction' phrase suggests two modes but does not clarify when to prefer one over the other or when to use a different tool.

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