Skip to main content
Glama

pmux_agent_status

Return a no-wait status snapshot for an agent, including tab liveness, provider readiness, and optional completion or runtime error detection.

Instructions

Primary agent orchestration tool: return a no-wait v2.1 status snapshot. Use pmux_tab_status/pmux_capture_pane only as low-level fallbacks. Includes tab alive, provider-specific readiness, optional DONE signal for agentId/turn/requestId, optional report-file check, runtimeError when detected, and pane tail. No server-side state is kept.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
turnNoOptional turn number. Used with agentId for DONE/report-file status.
tabIdYesTarget tab id (from pmux_list_tabs / pmux_create_tab).
agentIdNoOptional agent id. When omitted, status returns readiness only.
providerYes
requestIdNoOptional caller-owned request id using the same format as agentId.
busyPatternNobusyPattern regex override. Max 200 chars; compile errors become ToolError.
workspaceIdYesTarget workspace id (from pmux_list_workspaces).
errorPatternNoerrorPattern regex override. Max 200 chars; compile errors become ToolError.
readyPatternNoreadyPattern regex override. Max 200 chars; compile errors become ToolError.
runtimeErrorPatternNoruntimeErrorPattern regex override. Max 200 chars; compile errors become ToolError.
Behavior5/5

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

Describes what status includes (tab alive, readiness, DONE signal, report-file check, runtimeError, pane tail) and explicitly states no server-side state kept, which is crucial for an orchestration tool.

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 that front-load purpose and are free of fluff.

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?

Covers all major output aspects and state behavior, though no output schema exists; minor gaps on response format but adequate for the complexity.

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?

Schema has high description coverage (90%), but description adds context on how agentId/turn/requestId relate to DONE signal and report-file check, enhancing understanding beyond 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?

Clearly states it returns a no-wait status snapshot for agent orchestration, distinguishes itself as primary tool and mentions siblings as low-level fallbacks.

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 advises to use this as primary tool and pmux_tab_status/pmux_capture_pane only as low-level fallbacks, providing clear when-to-use guidance.

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/yoway030/purplemux-mcp'

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