Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_monitor

Monitor CPU, RAM, disk, network, and process usage on remote servers to track system performance and resource utilization.

Instructions

Monitor system resources (CPU, RAM, disk) on remote server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name from configuration
typeNoType of monitoring (default: overview)
intervalNoUpdate interval in seconds for continuous monitoring
durationNoDuration in seconds for continuous monitoring

Implementation Reference

  • Registration of the 'ssh_monitor' tool within the monitoring group in the TOOL_GROUPS export, used for tool registration and configuration management.
    // Monitoring group (6 tools) - System health and monitoring
    monitoring: [
      'ssh_health_check',
      'ssh_service_status',
      'ssh_process_manager',
      'ssh_monitor',
      'ssh_tail',
      'ssh_alert_setup'
    ],
  • Core helper functions for comprehensive system monitoring, including building multi-metric health check commands (CPU, memory, disk, load, uptime, network) and parsing results into structured data with health status. Likely used by the ssh_monitor tool handler.
    export function buildComprehensiveHealthCheckCommand() {
      return `
        echo "=== CPU ==="
        ${buildCPUCheckCommand()}
        echo "=== MEMORY ==="
        ${buildMemoryCheckCommand()}
        echo "=== DISK ==="
        ${buildDiskCheckCommand('all')}
        echo "=== LOAD ==="
        ${buildLoadAverageCommand()}
        echo "=== UPTIME ==="
        ${buildUptimeCommand()}
        echo "=== NETWORK ==="
        ${buildNetworkCheckCommand()}
      `.trim();
    }
    
    /**
     * Parse comprehensive health check output
     */
    export function parseComprehensiveHealthCheck(output) {
      const sections = output.split('=== ').filter(s => s);
      const result = {};
    
      for (const section of sections) {
        const [name, ...content] = section.split('\n');
        const data = content.join('\n').trim();
    
        switch (name.toLowerCase().trim()) {
        case 'cpu ===':
          result.cpu = parseCPUUsage(data);
          break;
        case 'memory ===':
          result.memory = parseMemoryUsage(data);
          break;
        case 'disk ===':
          result.disks = parseDiskUsage(data);
          break;
        case 'load ===':
          result.load_average = data;
          break;
        case 'uptime ===':
          result.uptime = data;
          break;
        case 'network ===':
          result.network = parseNetworkStats(data);
          break;
        }
      }
    
      // Determine overall health
      if (result.cpu && result.memory && result.disks) {
        result.overall_status = determineOverallHealth(result.cpu, result.memory, result.disks);
      }
    
      return result;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It lacks details on authentication needs, rate limits, output format, whether it's read-only or has side effects, or how continuous monitoring works. This is inadequate for a tool with multiple parameters and no output schema.

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?

Single sentence, front-loaded with the core purpose, zero wasted words. It efficiently communicates the essential function without unnecessary elaboration, making it easy for an agent to parse quickly.

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?

For a monitoring tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how errors are handled, or behavioral traits like whether it's passive monitoring or triggers actions. Given the complexity and lack of structured data, more context is needed for effective agent use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents parameters. The description adds no additional meaning beyond implying monitoring of CPU, RAM, and disk, which partially aligns with the 'type' enum but doesn't explain semantics like what 'overview' includes or how 'interval' and 'duration' interact. Baseline 3 is appropriate given high schema coverage.

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 clearly states the action ('monitor') and resource ('system resources on remote server'), specifying CPU, RAM, and disk as examples. It distinguishes from most siblings by focusing on monitoring rather than execution, backup, or session management, though it doesn't explicitly differentiate from similar tools like ssh_health_check.

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?

No explicit guidance on when to use this tool versus alternatives like ssh_health_check or ssh_process_manager. The description implies monitoring system resources but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bvisible/mcp-ssh-manager'

If you have feedback or need assistance with the MCP directory API, please join our Discord server