Skip to main content
Glama
Sign In
terminal-x-mcp

terminal-x-mcp

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

plan_workflow

Plan multi-step terminal workflows by defining a goal, listing commands, and setting dependencies to ensure ordered execution.

Instructions

Plan a multi-step terminal workflow

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": {
      "goal": "<goal>"
    },
    "name": "plan_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe workflow goal or objective
commandsNoList of commands to execute
dependenciesNoCommand dependencies and ordering

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-alpha.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It does not explicitly state whether the tool executes commands or merely returns a plan, nor does it mention side effects or safety characteristics. The verb 'plan' implies non-execution, but this is not explicit.

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?

The description is a single sentence with no filler, directly stating the core purpose. It is appropriately concise and front-loaded.

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?

Given the nested dependencies parameter, lack of output schema, and presence of execution siblings, the description is too sparse. It does not explain return behavior, the dependencies field, or how planning relates to execution, leaving critical gaps for effective usage.

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?

The schema has 100% parameter description coverage, so the description does not need to add parameter details. It doesn't add extra meaning beyond the schema, which is the baseline for full schema coverage.

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 provides a specific verb ('plan') and resource ('multi-step terminal workflow'), clearly distinguishing it from sibling tools like execute_command, which executes commands rather than plans them.

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?

The description offers no guidance on when to use this tool vs alternatives such as execute_command. It does not mention prerequisites, conditions for planning versus executing, or any exclusions.

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