Skip to main content
Glama

run_parallel

Execute multiple shell commands concurrently and collect exit codes, durations, and output tails to compare or batch diagnostic tasks.

Instructions

Run shell commands concurrently; exit codes, durations, output tails.

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": {
      "commands": "<commands>"
    },
    "name": "run_parallel"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
tailNo
commandsYes
timeout_sNo
concurrencyNo
stop_on_failureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses only that commands execute concurrently and what is returned. It says nothing about whether commands are killed on timeout, how stop_on_failure interacts with already-running commands, default concurrency, or the safety implications of executing arbitrary shell commands. These are material gaps for a tool that runs arbitrary processes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single semicolon-delimited clause is front-loaded and waste-free, but its brevity comes at the cost of under-specification rather than tight editing. Nothing is padded, yet very little is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter execution tool with no annotations, no output schema, and zero schema descriptions, this definition leaves too much unknown. An agent cannot determine timeout semantics, failure handling, default concurrency, or the shape of the reported results beyond three named fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely does not. 'Concurrently' weakly hints at the concurrency parameter and 'output tails' weakly hints at tail, but cwd, timeout_s, and stop_on_failure are entirely unexplained in both schema and description.

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?

States a specific verb and resource ('Run shell commands concurrently') plus the return content ('exit codes, durations, output tails'), so an agent knows exactly what the tool does. It does not distinguish itself from any sibling (e.g., cron or benchmark), which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer this over a single-command or sequential alternative, no prerequisites, and no exclusions. The only implicit signal is the word 'concurrently', which an agent must infer as the selection criterion.

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