Skip to main content
Glama

List tmux sessions

list_sessions
Read-only

Inspect every tmux/byobu session on the configured socket to see its working directory, foreground command, attached clients, last activity, and one-line preview; read-only.

Instructions

List every tmux/byobu session on the configured socket with its working directory, foreground command, attached clients, last activity, and a one-line preview. Read-only.

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_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=true, and the description restates that as "Read-only" (redundant) but adds genuinely new context: the operation is scoped to "the configured socket", so the agent knows the result set is limited to one server instance. It also discloses the shape of each returned record, which matters because there is no output schema. It stops short of noting cost, session-count limits, or behavior when no sessions exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the verb and scope, followed by a two-word safety note. The final "Read-only." duplicates readOnlyHint and could be dropped, but the wording is otherwise waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and safety already covered by annotations, the description carries exactly the load it needs to by describing the fields each row contains. An agent can decide to call it and interpret the result without further information.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema; baseline applies. The mention of "the configured socket" usefully signals that scope is not parameterizable here.

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?

"List every tmux/byobu session on the configured socket" pairs a specific verb with a specific resource and even enumerates the per-session fields returned (working directory, foreground command, attached clients, last activity, preview). That reads unmistakably differently from the mutating/inspecting siblings (capture, exec, kill_session, new_session, send_keys), though none of them are named explicitly.

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?

There is no when-to-use guidance, no mention of using this to discover session names before calling capture/exec/send_keys, and no exclusions. The agent must infer from the name alone that this is a discovery/enumeration step.

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