Skip to main content
Glama
nickgnd

Tmux MCP Server

by nickgnd

list-windows

Retrieve all windows from a specified tmux session to view and manage terminal workspace layouts.

Instructions

List windows in a tmux session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the tmux session

Implementation Reference

  • src/index.ts:81-106 (registration)
    MCP server.tool registration for the 'list-windows' tool, including description, input schema (sessionId), and inline async handler that calls tmux.listWindows and returns formatted JSON response or error.
    server.tool(
      "list-windows",
      "List windows in a tmux session",
      {
        sessionId: z.string().describe("ID of the tmux session")
      },
      async ({ sessionId }) => {
        try {
          const windows = await tmux.listWindows(sessionId);
          return {
            content: [{
              type: "text",
              text: JSON.stringify(windows, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error listing windows: ${error}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod input schema for the list-windows tool requiring a sessionId string parameter.
    {
      sessionId: z.string().describe("ID of the tmux session")
    },
  • Inline handler function for list-windows tool execution logic.
    async ({ sessionId }) => {
      try {
        const windows = await tmux.listWindows(sessionId);
        return {
          content: [{
            type: "text",
            text: JSON.stringify(windows, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error listing windows: ${error}`
          }],
          isError: true
        };
      }
    }
  • Core helper function listWindows that executes the tmux 'list-windows' command, parses the output using custom format, and returns array of TmuxWindow objects.
    export async function listWindows(sessionId: string): Promise<TmuxWindow[]> {
      const format = "#{window_id}:#{window_name}:#{?window_active,1,0}";
      const output = await executeTmux(`list-windows -t '${sessionId}' -F '${format}'`);
    
      if (!output) return [];
    
      return output.split('\n').map(line => {
        const [id, name, active] = line.split(':');
        return {
          id,
          name,
          active: active === '1',
          sessionId
        };
      });
    }
  • TypeScript interface defining the structure of TmuxWindow objects returned by the listWindows helper.
    export interface TmuxWindow {
      id: string;
      name: string;
      active: boolean;
      sessionId: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but reveals nothing about behavior: no indication of output format, whether it's read-only or has side effects, error conditions, or performance characteristics. 'List' implies a read operation, but this isn't explicitly confirmed.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple listing tool.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the output contains (e.g., window IDs, names, status), error handling, or behavioral constraints. While the tool is simple, the description leaves too much undefined for reliable agent use.

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?

Schema description coverage is 100%, so the schema already fully documents the single 'sessionId' parameter. The description adds no additional parameter context beyond implying windows are listed for a specific session. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and resource ('windows in a tmux session'), making the purpose immediately understandable. It distinguishes from siblings like 'list-sessions' and 'list-panes' by specifying windows, but doesn't explicitly contrast with other window-related tools like 'create-window' or 'kill-window'.

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 doesn't mention prerequisites (e.g., needing an existing session), when not to use it, or how it differs from similar tools like 'list-sessions' or 'list-panes' beyond the obvious resource difference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nickgnd/tmux-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server