termcp

run_sequence

Execute multiple shell commands in sequence, capturing variables from previous steps for use in later commands. Set working directory, per-command timeout, and stop-on-error.

Instructions

Execute multiple shell commands in sequence. Supports variable capture ($PREV, $STEP{n}).

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

Input Schema

Name	Required	Description
`cwd`	No	Working directory (default: home)
`commands`	Yes	List of commands to execute in order
`timeout_ms`	No	Per-command timeout in ms (default 30000)
`stop_on_error`	No	If true (default), stops when a command fails.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

B3.3/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. It usefully discloses the $PREV / $STEP{n} variable-capture mechanism, but for an arbitrary shell-execution tool it omits side effects, permissions, sandboxing, and how stop_on_error interacts with subsequent steps, leaving most behavioral traits undisclosed.

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 short sentences with zero filler; the core action is front-loaded and the variable-capture note is a compact, relevant addendum.

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?

With no output schema and no annotations, the description should cover more: what the result contains (per-command output, captured variables, exit status) and the error semantics of stop_on_error. For a four-parameter execution tool it is adequate but leaves meaningful gaps.

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 description coverage is 100%, so each of the four parameters is already documented in the schema and the baseline is 3. The description adds only the variable-capture syntax for commands, which is slightly beyond the schema but not a rich supplement.

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 ('Execute multiple shell commands in sequence') with the added scope of sequence execution, which inherently separates it from the single-command sibling run_command. It stops short of explicitly naming that sibling, so an agent must infer the boundary rather than read it.

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 phrase 'multiple shell commands in sequence' implies when this is preferable to run_command, and the mention of variable capture hints at the chaining use case. There is no explicit when-to-use/when-not statement or named alternative, so the guidance is only implied.

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

Deploy Server