tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

Python

Local

search_pane

Read-onlyIdempotent

Search a tmux pane's scrollback for regex matches, with configurable target and max results.

Instructions

Search pane scrollback history using regex pattern

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

Input Schema

Name	Required	Description	Default
`target`	No
`pattern`	No
`max_results`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover readOnly and idempotency. The description adds that the search uses regex and targets scrollback history, which complements the annotations. However, it does not disclose behavior like match limits or target requirements, leaving some gaps.

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 sentence with no filler, making it highly concise and front-loaded.

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?

Given the tool's simplicity and existing annotations/output schema, the description covers the core purpose but lacks parameter semantics and usage context. It is minimally adequate but has clear gaps for a 3-param tool with 0% schema coverage.

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 has 0% description coverage, so the description must compensate. It clarifies 'pattern' as a regex but leaves 'target' and 'max_results' unexplained. This is partial compensation, warranting a 2.

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 uses specific verb 'Search' with resource 'pane scrollback history' and method 'regex pattern', clearly distinguishing it from sibling tools like read_pane or list_panes.

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?

No explicit when/when-not guidance is provided, but the description implies the use case of searching scrollback. It does not mention alternatives or exclusions, scoring a 3.

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