tmux-mcp-server

by manhnv198669

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_windows

Read-onlyIdempotent

List tmux windows for a specific session or across all sessions to inspect current window layout.

Instructions

List tmux windows for a session or across all sessions

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

Input Schema

Name	Required	Description	Default
`target`	No
`all_sessions`	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.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, so the agent knows this is a safe read operation. The description adds behavioral context by specifying the two modes (session-specific or all sessions), which goes beyond the annotations and clarifies the tool's scope.

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, direct sentence that front-loads the action ('List') and the resource. Every word is purposeful, with no redundancy or filler, making it highly concise and well-structured.

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?

Given the tool's simplicity (two optional parameters, output schema present, and read-only annotations), the description covers its core purpose and operational modes. However, it omits details about default behavior and target format, which are minor but notable gaps for an agent that needs to invoke it correctly without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no descriptions for its two parameters (target and all_sessions), and the description partially compensates by explaining the 'for a session or across all sessions' behavior. However, it does not clarify the format of target (e.g., session name) or what happens when both parameters are at their defaults, leaving ambiguity.

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 tool lists tmux windows, with a specific scope (for a session or across all sessions). This distinguishes it from sibling tools like list_sessions and list_panes by explicitly naming the resource (windows) and the two operating modes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context that this tool can be used for a specific session or across all sessions, which implies when to use it. However, it does not explicitly mention alternatives or exclusion criteria, so it falls short of a 5 but is still useful and unambiguous.

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