safe-ssh-mcp

Overview Schema Source Related Servers Discussions Admin

get_crictl_ps

Collects all CRI containers, including exited ones, from a remote Linux host over SSH by running crictl ps --all, usually requiring root.

Instructions

Collects crictl ps --all output (all CRI containers on a kubernetes node, including exited ones: container ID, image, state, name, attempt, pod) from a remote Linux host via SSH. Usually requires root.

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_crictl_ps"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes
`port`	No
`user`	Yes
`timeout`	No
`key_path`	No
`password`	No
`accept_new_hostkey`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Nov 13, 2026

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 carries the burden and does disclose two meaningful traits: remote execution over SSH and that the listing is exhaustive (--all, including exited containers), plus the privilege requirement. It omits the safety profile (read-only), failure behavior on non-root, timeouts, and how authentication modes differ.

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?

A single tight sentence plus a field enumeration; the scope-defining detail ('including exited ones') is front-loaded and every clause earns its place.

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 output schema handles return values, and the description covers purpose, transport, and privilege needs. But for a 7-parameter SSH tool with zero schema descriptions, key gaps remain around authentication choice, host-key acceptance semantics, and timeout behavior.

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 seven parameters, and the description says nothing about host, port, user, key_path, password, timeout, or accept_new_hostkey. An agent must infer entirely from property names how to supply credentials or choose between key-based and password SSH auth.

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 ('Collects crictl ps --all output'), scopes it precisely to 'all CRI containers on a kubernetes node, including exited ones', and even enumerates the returned fields. It implicitly separates itself from the Docker sibling by naming crictl/CRI, but never explicitly contrasts with get_docker_ps_all or get_crictl_inspect.

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?

'Usually requires root' gives a prerequisite, and 'via SSH' plus 'remote Linux host' establishes context. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as get_crictl_inspect for detail or get_docker_ps_all for non-CRI containers.

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

Deploy Server