Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

runInTerminal

Destructive

Run a shell command in a specific terminal, wait for completion, and get exit code and output. Uses terminal name or index, with optional timeout.

Instructions

Execute command and wait for completion. Returns exit code and output. Prefer over runCommand.

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": {
      "command": "<command>"
    },
    "name": "runInTerminal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTerminal name (from listTerminals). Uses active if omitted.
showNoFocus terminal panel while running (default: true)
indexNoTerminal index (0-based) from listTerminals. Used if name omitted.
commandYesShell command to run (no metacharacters or newlines)
timeoutNoSeconds to wait for completion (default: 30, max: 300)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations destructiveHint and openWorldHint are present but description adds minimal beyond 'wait for completion'. No caution about side effects or external access.

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?

Single sentence plus recommendation, no wasted words, front-loaded with action.

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?

No output schema; description only says 'Returns exit code and output' without format details or error handling. Lacks behavioral context for a destructive/open-world tool.

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 covers all 5 parameters with full descriptions. Description adds no extra parameter details beyond the schema.

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?

Clearly states 'Execute command and wait for completion' with return values. Distinguishes from sibling 'runCommand' via direct recommendation.

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?

Suggests preference over runCommand but lacks explicit conditions for use, prerequisites like listing terminals, or when to avoid.

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