serverkit-mcp

run_command

Run shell commands over SSH on a remote server. Requires start_session first and blocks sudo, doas, su, and pkexec.

Instructions

Run a shell command on the server ServerKit is connected to over SSH. Requires start_session first. Blocked if the command invokes sudo/doas/su/pkexec.

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	Default
`cwd`	No
`command`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Sep 12, 2026

TDQS

A3.8/5.0

Behavior3/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 usefully discloses the session prerequisite and the blocked-command policy, but says nothing about blocking vs. async behavior, timeouts, how stdout/stderr are returned, or the destructive potential of running arbitrary shell commands.

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?

Three short sentences, each earning its place: the action, the prerequisite, and the restriction. The primary verb+resource is front-loaded and nothing is repeated.

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?

For a 2-parameter command-execution tool with no annotations and no output schema, the definition covers the essential prerequisite and the key restriction, which is enough to call it. It remains incomplete on cwd semantics, execution/output behavior, and timeout or failure handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 2 parameters. The description conveys only the obvious meaning of 'command'; the 'cwd' parameter is never mentioned, leaving its semantics (working directory relative to what base? default value?) undocumented in both schema and description.

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?

States a specific verb and resource ('Run a shell command on the server... over SSH'), and the sudo/doas/su/pkexec block immediately distinguishes it from the sibling run_command_sudo. An agent can route between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the prerequisite ('Requires start_session first') and the negative condition that disqualifies this tool (sudo-invoking commands), which implicitly routes the caller to run_command_sudo. It stops short of naming that sibling or describing what to do if the command is blocked.

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

Deploy Server