Skip to main content
Glama
laszlopere

mcp-tmux

by laszlopere

tmux_stream_read

Read-only

Long-poll new events from a tmux stream, blocking until output or timeout. Returns events like output, window-add, and layout-change, filterable by pane or kind.

Instructions

Long-poll new events from a stream (blocks until output or timeout).

Returns {"events", "cursor", "alive", "lagged"}. Each event has a seq, a type ("output", "window-add", "layout-change", "exit", ...) and, where relevant, pane/window/session ids and data. For "output" events data is the decoded pane text (ANSI stripped unless strip_ansi=False).

Filter with pane (e.g. "%0") and/or kinds (e.g. ["output"]). The cursor auto-advances between calls, so just call again to get the next batch; pass an explicit cursor to re-read from a known point. lagged is true if the buffer overflowed and some events were dropped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stream_idYes
timeoutNo
max_eventsNo
paneNo
kindsNo
cursorNo
strip_ansiNo
Behavior5/5

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

Describes blocking behavior, return format, filtering, cursor mechanics, and lagged flag. Consistent with readOnlyHint annotation, adding context beyond annotations.

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?

Well-structured with front-loaded purpose, then return format, then parameter details. Every sentence adds value with no redundancy.

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?

Despite no output schema, description fully covers return values structure, event types, filtering options, and edge cases like lagged overflow.

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

Parameters5/5

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

With 0% schema coverage, the description explains all parameters including timeout, max_events, pane, kinds, cursor, and strip_ansi, adding meaning beyond the 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 'Long-poll new events from a stream' with specific verb and resource, distinguishing it from sibling tools like tmux_stream_start or tmux_stream_list.

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?

Explains when to use it (to get new events with blocking) and how cursor auto-advances, but doesn't explicitly state when not to use or list alternatives, though sibling differentiation is clear.

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/laszlopere/mcp-tmux'

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