tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

zoom_pane

Maximize or restore any tmux pane by toggling its zoom state. Focus on a pane instantly, then return to the full layout.

Instructions

Toggle zoom state (maximize/restore) for target pane

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

Input Schema

Name	Required	Description	Default
`target`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description adds the key behavioral context that the operation is a toggle, which aligns with annotations readOnlyHint=false and idempotentHint=false. However, it does not disclose any additional side effects (e.g., what happens if the pane is already zoomed, or if the target is invalid), relying on the agent's tmux knowledge.

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 that directly communicates the tool's purpose with no unnecessary words. It is appropriately sized for a simple toggle operation.

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

Completeness3/5

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

For a simple tool with one optional parameter and an output schema, the description covers the core behavior but omits details about expected inputs and error conditions. Given the tool's simplicity, this is acceptable but not thorough; a note about target syntax or default behavior would improve completeness.

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?

With schema description coverage at 0%, the description must compensate, but it only mentions 'target pane' without specifying the expected format (e.g., pane ID, index, or session:window.pane syntax). The schema only provides a default value with no additional explanation, so the description adds minimal value beyond the parameter name.

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 'Toggle zoom state (maximize/restore) for target pane' clearly states the action (toggle), the resource (pane), and the specific behavior (maximize/restore). It distinguishes this from sibling tools like resize_pane (which changes size) and select_pane (which changes focus).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or alternative tools to consider, leaving the agent to infer usage purely from the verb and context.

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