mcp-hostops

Overview Schema Source Related Servers Discussions Admin

Command in background

start

Destructive

Execute a command on a host in the background and return its job ID immediately, enabling long-running tasks to be tracked without blocking.

Instructions

Start a command on a host in the background and return its job id right away.

For long-running commands: output is collected with the job call. The job lives as long as the server does (within the session) and doesn't outlive it.

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

Input Schema

Name	Required	Description	Default
`cwd`	No	Same as run.	~
`host`	Yes	Alias from ~/.ssh/config.
`sudo`	No	Same as run.	auto
`command`	Yes	Command for the host's shell.

Output Schema

Name	Required	Description	Default
`id`	Yes
`cwd`	Yes
`host`	Yes
`error`	No	reason when status=error; empty otherwise
`status`	No		running
`command`	Yes
`exit_code`	No	return code; null — still running or killed

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false). The description adds valuable behavioral context beyond annotations: it returns a job id immediately, output is collected via the job call, and the job lives only as long as the server session. These details help the agent understand async behavior and output retrieval, though it does not cover auth requirements or rate limits.

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 front-loaded with the core action, followed by two short sentences that add critical details about output retrieval and job lifetime. Every sentence earns its place, and there is no wasted text.

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

Completeness5/5

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

Given the tool's complexity, the 100% schema coverage, the presence of an output schema, and the annotations, the description provides everything an agent needs to invoke the tool correctly: async return, job id, output retrieval method, and session-bound lifetime. Nothing essential is omitted.

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 parameters (cwd, host, sudo, command) with types, defaults, and descriptions. The description does not add meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Start a command on a host in the background and return its job id right away.' It clearly distinguishes background execution from foreground execution, but does not explicitly name the sibling 'run' as the foreground alternative. This makes the purpose clear but leaves sibling differentiation to inference.

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 description hints at usage with 'For long-running commands: output is collected with the job call,' implying this tool is appropriate for long-running tasks. However, it does not explicitly state when to use this tool versus 'run', nor does it provide exclusions or prerequisites. The guidance is implied rather than explicit.

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

Deploy Server