Skip to main content
Glama
Sign In
tmux-mcp

tmux-mcp

by fr1sk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_windows

List all windows in a tmux session, showing index, name, pane count, and active status. Automatically selects the window if only one exists; otherwise prompts for user selection.

Instructions

List all windows in a tmux session. Returns window index, name, pane count, and active status. If there is only one window, auto-select it without asking. If multiple, ask the user which window to use.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>"
    },
    "name": "list_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesSession name (from list_sessions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses auto-select behavior and return fields, which is more than a simple list. No contradictions.

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?

Two sentences: first defines purpose and output, second explains behavior. No wasted words, front-loaded with key information.

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 single parameter and no output schema, description covers functionality and behavior adequately. Missing aspects like error handling but not critical for a list tool.

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?

Only parameter 'session' with description 'Session name (from list_sessions)' adds value beyond schema by referencing another tool. Schema coverage is 100% so baseline 3, plus extra context earns 4.

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?

Description states 'List all windows in a tmux session' with specific return fields (index, name, pane count, active status). Clearly distinguishes from siblings list_sessions and 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 Guidelines4/5

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

Describes auto-select behavior for single window and ask-user for multiple, but lacks explicit when-to-use vs alternatives. Context is clear but no direct exclusions.

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

Deploy Server

Other Tools