Tunnel Manager

Run Command

tm_remote_run_command

Runs shell commands on a remote SSH host using shared connection settings, enabling single-host command execution without separate SSH setup.

Instructions

Run command (tm_remote). Single-host SSH operations with shared connection params.

Input Schema

Name	Required	Description	Default
`cfg`	No	SSH config path; unset uses ~/.ssh/config.
`cmd`	No	Shell command (run_command).
`key`	No	Key path (test_key_auth/setup_passwordless).
`host`	No	Inventory alias, or a raw hostname with an explicit user.
`lcfg`	No	Local SSH config (copy_ssh_config).
`port`	No	Port; unset uses the inventory alias, else 22.
`rcfg`	No	Remote SSH config (copy_ssh_config).	/root/.ssh/config
`user`	No	Username; unset uses the inventory alias.
`lpath`	No	Local file path (send_file/receive_file).
`proxy`	No	Teleport proxy; unset uses the alias.
`rpath`	No	Remote file path (send_file/receive_file).
`confirm`	No	Confirm a destructive action (remove_host_key) without elicitation.
`id_file`	No	Private key path; unset uses the alias.
`new_key`	No	New private key path (rotate_key).
`timeout`	No	Command timeout in seconds.
`key_type`	No	Key type: rsa or ed25519 (setup_passwordless/rotate_key).	ed25519
`certificate`	No	Teleport certificate; unset uses the alias.
`known_hosts`	No	Known hosts path (remove_host_key).	/root/.ssh/known_hosts
`password_ref`	No	Runtime secret reference for the SSH password; unset uses the alias.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv3.4.6Oct 31, 2026

changedInput schema / properties / certificate / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / certificate / description

Previous value: -"Teleport certificate."New value: +"Teleport certificate; unset uses the alias."

addedInput schema / properties / cfg / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / cfg / default

Previous value: -"/root/.ssh/config"New value: +null

changedInput schema / properties / cfg / description

Previous value: -"SSH config path."New value: +"SSH config path; unset uses ~/.ssh/config."

removedInput schema / properties / cfg / type
```
Removed value: -"string"
```

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Confirm a destructive action (remove_host_key) without elicitation.",
+  "type": "boolean"
+}

changedInput schema / properties / host / description

Previous value: -"Remote host."New value: +"Inventory alias, or a raw hostname with an explicit user."

changedInput schema / properties / id_file / default

Previous value: -"/app/.ssh/id_ed25519"New value: +null

changedInput schema / properties / id_file / description

Previous value: -"Private key path."New value: +"Private key path; unset uses the alias."

changedInput schema / properties / password_ref / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / password_ref / description

Previous value: -"Runtime secret reference for the SSH password."New value: +"Runtime secret reference for the SSH password; unset uses the alias."

addedInput schema / properties / port / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / port / default
```
Previous value: -22New value: +null
```

changedInput schema / properties / port / description

Previous value: -"Port."New value: +"Port; unset uses the inventory alias, else 22."

removedInput schema / properties / port / type
```
Removed value: -"integer"
```
changedInput schema / properties / proxy / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / proxy / description

Previous value: -"Teleport proxy."New value: +"Teleport proxy; unset uses the alias."

changedInput schema / properties / user / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / user / description

Previous value: -"Username."New value: +"Username; unset uses the inventory alias."

Addedv3.3.1Oct 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds only the vague phrase 'shared connection params' and says nothing about execution side effects, privilege level, timeout behavior, or what happens when the remote command fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with zero filler. It is efficient, though the terseness is a shortfall captured under contextual completeness rather than a structure problem.

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?

This is a 19-parameter tool where only a handful apply to command execution; the description never says which, so an agent must reverse-engineer intent from per-param 'used by X' notes. Output schema and annotations cover returns and safety, but the core question of which params matter for this call is left unanswered.

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 every one of the 19 parameters is documented inline and the baseline is 3. The description does not identify which parameters (cmd, host, timeout) actually drive a run_command call, so it adds no meaning beyond the schema.

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 and resource (run a shell command over SSH) and scopes it to a single host, which implicitly contrasts with the bulk tm_inventory_run_command sibling. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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 guidance on when to use this versus tm_inventory_run_command, tm_remote_check_ssh, or the send/receive_file siblings. 'Single-host' is the only routing hint, and it is never framed as a selection criterion.

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

Deploy Server