tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

Python

Local

read_pane

Read-onlyIdempotent

Read a tmux pane's visible text and scrollback history to access past output and current terminal content.

Instructions

Read visible text and scrollback history from a 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": "read_pane"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No
`lines`	No
`start`	No
`target`	No
`full_history`	No
`include_colors`	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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'Read' is consistent, so no contradiction. However, the description adds no additional behavioral context beyond what annotations provide, such as output formatting, pane selection behavior, or performance implications.

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 concise sentence that is front-loaded with the key verb and resource, and contains no unnecessary words. It is efficient and well-structured.

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?

With 6 parameters, no description coverage, and no usage guidance, the tool is under-described for its complexity. The output schema exists, but the description still needs to cover parameter behavior and selection logic, which it does not.

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?

Schema description coverage is 0%, and the description does not explain any of the 6 parameters. It vaguely hints at scrollback vs visible text, but fails to clarify start/end/lines/target/include_colors or their defaults, leaving the agent to infer without sufficient info.

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 ('Read') and the resource ('pane') with specific scope ('visible text and scrollback history'), distinguishing it from sibling tools like get_pane_info (metadata) and search_pane (searching). It is a specific and unambiguous statement.

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 guidance is provided on when to use this tool versus alternatives such as search_pane or list_panes. The description does not mention prerequisites, exclusions, or situations where another tool would be more appropriate.

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