Skip to main content
Glama
safe-ssh-mcp

safe-ssh-mcp

by Areso

get_docker_ps_all

Collect all Docker container information (including stopped containers) from a remote Linux host over SSH, using passwordless sudo or doas if the login user cannot access the Docker daemon.

Instructions

Collects docker ps --all output from a remote Linux host via SSH When the login user cannot reach the docker daemon (not root, not in the docker group), the command is run through passwordless sudo or doas (sudo -n / doas -n).

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>",
      "user": "<user>"
    },
    "name": "get_docker_ps_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo
userYes
timeoutNo
key_pathNo
passwordNo
accept_new_hostkeyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.14

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing the execution path: SSH to a remote host and, when the login user lacks daemon access, re-running through passwordless sudo -n or doas -n. It does not say what happens when passwordless elevation is unavailable (failure mode), nor how authentication or timeouts are handled.

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 sentences, front-loaded with the action and resource, with no filler. The second sentence is a dense run-on that buries the sudo/doas caveat in parentheticals, costing a bit of readability.

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?

An output schema exists, so return values need not be explained, and the elevation behavior is covered. But for a 7-parameter SSH tool with zero annotation coverage, the authentication options, host-key verification default, and timeout semantics are left entirely undocumented.

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 7 parameters, so the description must carry the load and largely does not. It only implicitly clarifies that 'user' is the SSH login user (not a docker-level identity); port, timeout, key_path, password, and accept_new_hostkey get no meaning from the description at all.

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 concrete command and resource: 'Collects docker ps --all output from a remote Linux host via SSH'. The '--all' qualifier makes it distinguishable from a running-containers listing and from siblings like get_docker_images or get_docker_inspect without needing the schema.

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 pick this over get_docker_stats, get_docker_inspect, or get_crictl_ps, and no stated preconditions beyond the implicit need for SSH access. The elevation note is procedural detail, not tool-selection guidance.

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