Skip to main content
Glama
Sign In
tmux-shell

tmux-shell

by ketema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_tmux_sessions

Lists all tmux sessions, windows, and panes to identify active terminal targets for subsequent pane reading.

Instructions

Lists all available tmux sessions, windows, and panes. Use this to discover available targets before calling read_tmux_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": "list_tmux_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It implies no side effects by saying 'Lists', but does not explicitly state it is read-only or mention any requirements like tmux being running. Adequate but not thorough.

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 concise sentences: the first states the action, the second gives usage guidance. No fluff, front-loaded, and efficient.

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?

No output schema, so the description should explain the format of the returned data (e.g., names, IDs, structure). It says 'lists' but lacks details on what fields are provided. Also missing error conditions or prerequisites like tmux being available.

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?

There are no parameters, so schema coverage is 100%. The description adds value by clarifying what exactly is listed (sessions, windows, and panes), beyond just the parameterless schema.

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 it lists tmux sessions, windows, and panes, which is specific and distinguishes it from the sibling tool read_tmux_pane that reads a specific pane.

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

Usage Guidelines5/5

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

Explicitly states to use this tool before calling read_tmux_pane to discover available targets, providing clear guidance on when to use it and implying its role as a prerequisite.

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