Skip to main content
Glama
Sign In
purplemux-mcp

purplemux-mcp

by yoway030
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pmux_create_tab

Creates a new tab in a specified workspace, supporting terminal, claude-code, codex-cli, agent-sessions, web-browser, or diff panel types.

Instructions

Create a tab in a workspace. panelType is one of terminal | claude-code | codex-cli | agent-sessions | web-browser | diff (default terminal); invalid → 400 with validPanelTypes. WARNING: claude-code/codex-cli panelType creates a UI panel, NOT a managed agent session — the pane may be an empty shell before the UI attaches, and sending prompts into it is unreliable. To run a subagent, use pmux_agent_start instead (it launches the CLI in a terminal tab under full protocol control). Creating claude-code/codex-cli without the CLI installed → 409 with suggestedCommand. Returns the created-tab object.

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>"
    },
    "name": "pmux_create_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional display name for the tab.
panelTypeNoOne of terminal | claude-code | codex-cli | agent-sessions | web-browser | diff. Defaults to terminal.
workspaceIdYesTarget workspace id (from pmux_list_workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: panelType creates UI panel not agent, sending prompts is unreliable, and error responses include validPanelTypes and suggestedCommand.

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?

Concise, front-loaded with main action, and efficient use of sentences covering warnings, errors, and alternatives without 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?

Given tool complexity and no output schema, the description covers purpose, parameter nuances, error conditions, sibling differentiation, and behavioral caveats fully.

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 coverage is 100%, but description adds value by explaining panelType enum with default and error behavior, workspaceId source (pmux_list_workspaces), and name as optional display name.

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 the verb 'Create' and the resource 'tab in a workspace', specifies panelType options with defaults, and distinguishes from sibling pmux_agent_start for certain panel types.

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 warns against using this tool for agent panels (claude-code/codex-cli) by directing to pmux_agent_start, and mentions error conditions for invalid panelType (400) and missing CLI (409).

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