termcp

run_command

Executes local shell commands and returns stdout, stderr, and exit code, so agents can inspect system state or automate tasks. Supports working directories, stdin, timeouts, and tmux sessions.

Instructions

Execute a shell command locally. Returns stdout, stderr, and exit code.

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": "run_command"
  }
}

Input Schema

Name	Required	Description
`cwd`	No	Working directory (default: home)
`stdin`	No	Optional string to pipe to command stdin
`command`	Yes	The shell command to execute
`session_id`	No	If provided, run inside this tmux session
`timeout_ms`	No	Timeout in ms (default 30000, max 300000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

B3.1/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 burden. It discloses local execution and the return shape (stdout, stderr, exit code), but says nothing about side effects, permissions, sandboxing, or the fact that arbitrary commands can mutate or destroy the host — a substantial omission for a shell-execution tool.

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 sentences, front-loaded with the action and followed by the return contract. Nothing is wasted and there is no filler.

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?

The description compensates for the missing output schema by naming the return values, which is helpful. But for a no-annotation, arbitrary-shell tool it omits the risk profile and execution semantics that an agent needs to invoke it safely.

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 the schema already documents all five parameters including cwd, stdin, session_id and the timeout bounds. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (Execute) and resource (shell command) plus the scope 'locally', and names the return values. It does not distinguish itself from sibling run_sequence, which likely also runs commands, so it stops short of 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 when-to-use guidance and no mention of alternatives. An agent cannot tell from the description whether to prefer run_sequence for multiple commands, start_process for long-running work, or create_session before using session_id.

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

Deploy Server