purplemux-mcp

Overview Schema Source Related Servers Discussions Admin

pmux_tab_status

Retrieve runtime status of a specific tab in a workspace. Provides alive status and other runtime info; for Electron tabs, alive:false is normal.

Instructions

Get tab runtime status. NOTE: for web-browser tabs alive:false is NORMAL (they are Electron webviews, not tmux) — probe health via the browser tools instead. claudeSessionId is a legacy alias of agentSessionId (same value).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "tabId": "<tabId>"
    },
    "name": "pmux_tab_status"
  }
}

Input Schema

Name	Required	Description	Default
`tabId`	Yes	Target tab id (from pmux_list_tabs / pmux_create_tab).
`workspaceId`	Yes	Target workspace id (from pmux_list_workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It adds behavioral context (alive:false is normal, legacy alias) but does not cover side effects, auth requirements, rate limits, or error conditions. It provides some transparency but not comprehensively.

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 are front-loaded with the core purpose. Every sentence adds value, with no waste. Highly 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?

Given no output schema, the description lacks information about return values. It provides some special notes but is incomplete regarding what the tool outputs, which is important for a status tool.

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 coverage is 100%, so baseline is 3. The description adds no new meaning to the parameters beyond what the schema already provides. The note about claudeSessionId is not related to input parameters and may be confusing.

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 'Get tab runtime status', which is a specific verb and resource. It adds context about web-browser tabs and a legacy alias, distinguishing it from similar tools like pmux_get_tab by focusing on runtime status. However, it does not explicitly differentiate from sibling tools.

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

Usage Guidelines3/5

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

The description provides mild usage guidance by noting that alive:false is normal for web-browser tabs and suggesting to use browser tools for health checks. It does not explicitly state when to use this tool versus alternatives like pmux_get_tab or pmux_list_tabs.

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