Skip to main content
Glama
Sign In
mcpHydroSSH

mcpHydroSSH

by hydroCoderClaud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_help

Access help and usage examples for SSH remote server management. Select a topic such as config, connect, exec, auth, or examples to get specific guidance.

Instructions

Show help and usage examples for mcpHydroSSH

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": "ssh_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoSpecific topic to get help on (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description fails to disclose the tool's read-only nature or any side effects. It only states it shows help, but does not explain that no state changes occur or what the output format is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is concise and front-loaded. However, it lacks any structured breakdown of usage or output details, which could be beneficial.

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?

Given the simplicity of the tool (one optional parameter, no output schema), the description is minimally adequate but does not explain the output format or provide examples, leaving some ambiguity.

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 input schema is fully described with 100% coverage, listing the optional 'topic' parameter with enum values. The description does not add meaning beyond the schema, so the baseline score of 3 applies.

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 'Show help and usage examples for mcpHydroSSH' clearly states the tool's function: providing help and examples for the SSH server. It distinguishes from sibling tools that perform actions like connecting or executing commands.

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 guidance is provided on when to use this tool versus sibling tools. It does not clarify that this tool is for learning about other tools or obtaining examples, nor does it exclude any use cases.

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