safe-ssh-mcp

Overview Schema Source Related Servers Discussions Admin

get_crictl_images

Collects crictl images output from a remote Kubernetes node via SSH, including image, tag, ID, and size, to inspect CRI runtime images.

Instructions

Collects crictl images output (image, tag, image ID, size of images present in the CRI runtime of a kubernetes node) 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_images"
  }
}

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.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the SSH transport, the root privilege requirement, and the exact data collected. It says nothing about host-key verification behavior (accept_new_hostkey defaults to false), timeout semantics, or credential handling, which matter for a remote-execution tool.

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?

A single sentence with a compact field list plus a short privilege note; the essential information is front-loaded. The parenthetical enumeration is dense but useful rather than redundant filler.

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?

An output schema exists, so return values need no explanation, but with seven fully undocumented parameters and no annotations the definition leaves an agent guessing about authentication mode, host-key acceptance, and timeout defaults. For a remote-SSH tool with this many inputs, the description should do more.

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 coverage is 0% across seven parameters, so the description would need to compensate, and it does not: host, user, port, timeout, key_path, password, and accept_new_hostkey are never mentioned. Only 'remote Linux host via SSH' loosely hints at the connection parameters.

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?

A specific verb ('Collects') plus resource ('crictl images output') and an enumeration of the returned fields (image, tag, image ID, size), scoped to 'the CRI runtime of a kubernetes node'. That implicitly separates it from get_docker_images, though it never names that sibling explicitly.

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 phrase 'of a kubernetes node' implies the CRI/containerd use case as opposed to Docker, and 'Usually requires root' is a useful prerequisite. There is no explicit when-to-use statement and no named alternative telling an agent when to pick this over get_crictl_inspect_image or get_docker_images.

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

Deploy Server