Skip to main content
Glama
Sign In
purplemux-mcp

purplemux-mcp

by yoway030
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pmux_list_workspaces

Obtain workspace IDs by listing all purplemux workspaces. This tool is the entry point for workspace management, providing IDs required by other workspace tools.

Instructions

List purplemux workspaces: { workspaces:[{id,name,directories}] }. Start here to get workspaceId values for the other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pmux_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 correctly identifies a read-only list operation with no side effects. However, it does not mention authentication requirements or performance characteristics, but for a simple listing tool, the transparency is adequate.

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 efficient sentences: first describes output structure, second gives usage guidance. No superfluous words, front-loaded with key information.

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 explicitly reveals return format (workspaces with id, name, directories) and explains importance for other tools. Complete for a simple listing tool with clear context among siblings.

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?

Tool has no parameters (0 params), so description cannot add parameter semantics. Baseline of 4 is appropriate per guidelines.

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?

Description clearly states 'List purplemux workspaces' with specific verb and resource, and explicitly says it provides workspaceId for other tools, distinguishing it among siblings. Purpose is immediately clear and actionable.

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?

Explicitly states 'Start here to get workspaceId values for the other tools,' providing clear guidance that this is the entry point. Lacks explicit alternatives or when-not-to-use, but the role as first step is well communicated.

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