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

rootpilot-ssh-diagnose

by Easton-OU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List the read-only command whitelist

get_whitelist

Lists all approved read-only SSH commands available on remote servers. Displays each command's key, purpose, shell template, and container requirement to clarify diagnostic capabilities.

Instructions

Return every command this server can run: key, purpose, shell template, and whether it needs a container argument. This is the complete set — nothing outside it can be executed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_whitelist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses that it returns a complete set and lists the fields, indicating a read-only operation without side effects. Since no annotations are provided, the description adequately conveys the behavior, though it doesn't mention authentication or rate limits.

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 two sentences, no redundancy, and immediately states the action and what is returned. It is well-structured and front-loaded.

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

Completeness5/5

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

Given the lack of parameters and output schema, the description provides sufficient information: it lists the fields returned and emphasizes completeness. This fully meets the needs for a simple listing tool.

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?

The input schema has no parameters, but the description adds value by detailing the return fields (key, purpose, shell template, container argument flag), which is not specified in the schema or output schema.

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 explicitly states it returns every command the server can run with specific details (key, purpose, shell template, container argument requirement). It distinguishes from sibling tools which involve collecting or listing hosts, clearly indicating this is for listing the command whitelist.

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

Usage Guidelines4/5

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

The description makes it clear that this tool is for retrieving the complete set of executable commands. While it doesn't explicitly state when not to use it or provide alternatives, the context and sibling tool names imply its standalone role for whitelist inspection.

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