Skip to main content
Glama
safe-ssh-mcp

safe-ssh-mcp

by Areso

get_memory_pressure

Retrieves memory pressure from a remote host over SSH when supported; deprecated—use get_pressure for CPU, I/O, and memory pressure in one call.

Instructions

DEPRECATED: use get_pressure, which returns CPU, I/O and memory pressure in one call. Returns memory pressure if supported

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

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

A4/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 two useful traits: the tool is deprecated and its result is conditional ('if supported'), implying platform-dependent failure or empty results. It says nothing about the fact that this is a remote SSH operation requiring host/user credentials, nor about timeouts or failure modes, which matters for a 7-parameter tool with zero annotation coverage.

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 short sentences, with the deprecation warning front-loaded before the functional statement. Nothing is redundant and the most decision-relevant information comes first.

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-value explanation is not required, and the deprecation redirect is the single most important thing an agent needs. Still, for a 7-parameter SSH tool with no annotations, the description omits connection/auth expectations and what 'if supported' means in practice, leaving gaps for anyone who must actually invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven parameters (host, port, user, timeout, key_path, password, accept_new_hostkey), and the description adds no meaning for any of them. However, the parameter names are conventional SSH connection fields that are largely self-explanatory, and the description is a deprecation notice rather than a usage guide.

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 ('Returns memory pressure') and immediately distinguishes itself from the sibling get_pressure, which covers CPU, I/O and memory in one call. The trailing 'if supported' leaves the exact scope slightly fuzzy, but an agent can tell what this tool does and how it differs from the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent away from this tool: 'DEPRECATED: use get_pressure, which returns CPU, I/O and memory pressure in one call.' That is both a when-not-to-use statement and a named, justified alternative — exactly the guidance an agent needs to avoid picking the deprecated path.

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