Skip to main content
Glama
safe-ssh-mcp

safe-ssh-mcp

by Areso

get_top

Collects a real-time top snapshot from a remote Linux host over SSH, including BusyBox/Alpine variants, to inspect CPU, memory, and process usage without modifying the system.

Instructions

Collects top's snapshot from a remote Linux host via SSH (top -b -n 1 -c). On BusyBox hosts (Alpine), where top has no -c, the output is plain top -b -n 1: its first line starts with '# BusyBox' and the columns differ.

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

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/5.0
Behavior3/5

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

With zero annotations the description must carry the full behavioral burden, and it does disclose valuable specifics: the transport (SSH), the exact commands issued, and the fact that Alpine/BusyBox output differs in first line and column layout. It is silent on authentication expectations (key vs. password), timeout semantics, and what happens on connection failure — meaningful gaps for a tool with seven parameters.

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?

Two sentences, front-loaded with the primary action and followed by the platform-specific caveat; every clause carries information and there is no 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?

The presence of an output schema removes the need to explain return values, but for a seven-parameter remote-execution tool with no annotations and 0% schema coverage, the definition leaves connection and authentication semantics entirely to inference.

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, so the description is obliged to compensate and largely does not. Only an indirect hint exists — 'remote Linux host via SSH' implies host, port, and credential parameters — but nothing explains `timeout`, `accept_new_hostkey`, or when `key_path` versus `password` applies.

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 names a specific verb and resource — collecting a `top` snapshot from a remote Linux host — and pins down the exact mechanism (`top -b -n 1 -c` over SSH). It does not, however, contrast itself with the many sibling process-inspection tools, so an agent still has to infer when this beats `get_ps_aux_top_cpu_consumers`.

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 explicit when-to-use or when-not-to-use statement and no named alternative, despite several siblings that surface process data. The BusyBox note explains a behavioral variant, not a selection criterion, so routing guidance is essentially absent.

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