Skip to main content
Glama
Sign In
purplemux-mcp

purplemux-mcp

by yoway030
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pmux_capture_pane

Capture current pane snapshot as text content. Use this low-level fallback for manual pane inspection when agent orchestration tools are not suitable.

Instructions

Low-level fallback for manual pane inspection; for agent orchestration prefer pmux_agent_* tools. Capture the current pane snapshot as { content }. Not meaningful for web-browser tabs. 409 'Tab session is not running' if the session is dead.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesTarget tab id (from pmux_list_tabs / pmux_create_tab).
workspaceIdYesTarget workspace id (from pmux_list_workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions return format as { content } and a 409 error condition. However, it does not explicitly state read-only nature or other behavioral traits like side effects, leaving some gaps.

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?

Three sentences, each serving a purpose: purpose, usage guidance, and error condition. No wasted words.

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?

Given low-level nature and no output schema, description covers purpose, usage, and a common error. However, it could have elaborated on output format to fully compensate for missing output schema.

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% with descriptions for both parameters. The description does not add extra meaning beyond what's already in the schema, so baseline of 3 applies.

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 captures a pane snapshot and distinguishes from higher-level pmux_agent_* tools. The verb 'capture' and resource 'pane snapshot' are explicit.

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 says when to use (low-level fallback) and when not (prefer pmux_agent_* tools). Also notes it's not meaningful for web-browser tabs, providing clear context.

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