Skip to main content
Glama
Sign In
rootpilot-ssh-diagnose

rootpilot-ssh-diagnose

by Easton-OU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Collect the base overview

collect_base

Collects a base set of diagnostic outputs from a remote host for an initial health check, covering Docker processes, disk usage, memory, and uptime.

Instructions

Shortcut: run the base group (docker_ps, df, df_inode, free, uptime, dmesg_oom, docker_daemon) — a cheap first look at a host.

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>"
    },
    "name": "collect_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYeshost name from list_hosts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only lists sub-commands run, but does not mention side effects (likely read-only), permissions, or failure modes. The 'cheap' hint suggests low overhead but is vague.

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?

The description is a single, well-structured sentence that front-loads the tool's purpose and lists included commands. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter, comprehensive schema coverage, and sibling tools providing context, the description adequately covers the tool's purpose. Lacks mention of output format or side effects, but is sufficient for a simple 'collect' action.

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?

The parameter 'host' is fully described in the schema with coverage 100%, and the description adds no extra detail such as format or constraints. Baseline score of 3 is appropriate as no further value is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool collects a group of specific commands (docker_ps, df, etc.) as a 'first look' at a host. It distinguishes from siblings like 'collect' and 'container_deep_dive' by specifying the scope and purpose.

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 description implies it's for initial assessment ('cheap first look'), but does not explicitly state when to use versus alternatives like 'collect' or 'container_deep_dive'. No when-not-to-use guidance provided.

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

Deploy Server

Other Tools