Skip to main content
Glama

ssh_help

Get help and usage examples for connecting to and managing remote servers via SSH. Learn how to configure connections, execute commands, authenticate, and use practical examples.

Instructions

Show help and usage examples for mcpHydroSSH

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoSpecific topic to get help on (optional)

Implementation Reference

  • The handler logic for 'ssh_help' which calls getHelpContent and returns the result in an MCP-compliant response.
    case 'ssh_help': {
      const topic = args.topic as string | undefined;
      const helpContent = getHelpContent(topic);
      return {
        content: [
          {
            type: 'text',
            text: helpContent,
          },
        ],
      };
    }
  • The helper function that generates the actual help strings based on the provided topic.
    function getHelpContent(topic?: string): string {
      if (topic === 'config') {
        return `# Config Help
    
    **Config file location:** \`~/.hydrossh/config.json\`
    
    **Server fields:**
    - \`id\` (required): Unique server identifier
    - \`name\` (required): Display name
    - \`host\` (required): Server hostname or IP
    - \`port\`: SSH port (default: 22)
    - \`username\`: SSH username
    - \`authMethod\`: "agent" | "key" | "password" (default: "agent")
    - \`privateKeyPath\`: Path to private key (for "key" auth)
    - \`password\`: Password (for "password" auth)
    
    **Example:**
    \`\`\`json
    {
      "id": "my-server",
      "name": "My Server",
      "host": "1.2.3.4",
      "username": "root",
      "authMethod": "key",
      "privateKeyPath": "~/.ssh/id_rsa"
    }
    \`\`\``;
      }
    
      if (topic === 'connect') {
        return `# Connection Help
    
    **Tools:**
    - \`ssh_list_servers\` - List configured servers
    - \`ssh_connect\` - Connect to a server (params: serverId, timeout?)
    - \`ssh_get_status\` - Check connection status
    - \`ssh_disconnect\` - Disconnect from server
    
    **Note:** \`connectionId\` is optional for most tools - uses most recent connection if not provided.`;
      }
    
      if (topic === 'exec') {
        return `# Command Execution Help
    
    **Tool:** \`ssh_exec\`
    
    **Params:**
    - \`command\` (required): Command to execute
    - \`connectionId\` (optional): Which connection to use
    - \`timeout\` (optional): Command timeout in ms
    - \`cwd\` (optional): Working directory
    
    **Example:**
    \`\`\`json
  • src/index.ts:134-146 (registration)
    The registration of the 'ssh_help' tool, defining its name, description, and input schema.
    {
      name: 'ssh_help',
      description: 'Show help and usage examples for mcpHydroSSH',
      inputSchema: {
        type: 'object',
        properties: {
          topic: {
            type: 'string',
            description: 'Specific topic to get help on (optional)',
            enum: ['config', 'connect', 'exec', 'auth', 'examples'],
          },
        },
        required: [],
Behavior3/5

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

With no annotations provided, the description carries the full burden. It explains the tool displays help content, but lacks disclosure on return format (text vs structured), safety profile, or whether this operates offline without server configuration.

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 of 7 words with zero redundancy. Information is front-loaded and appropriately sized for a simple utility tool.

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?

Adequate for a simple help utility with one optional parameter and no output schema. While it could briefly mention the available topic categories, the description successfully conveys the tool's function without unnecessary verbosity.

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 coverage is 100% with the 'topic' parameter fully documented including enum values. The description does not mention the parameter, but per calibration guidelines, high schema coverage establishes a baseline of 3 without requiring compensation from the description.

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 provides a specific verb ('Show') and resource ('help and usage examples'), clearly distinguishing this from operational siblings like ssh_connect or ssh_exec. It precisely scopes the tool to the mcpHydroSSH system.

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 on when to use this tool versus alternatives, or when to use specific topics (config, auth, etc.). No mention of whether this requires an active connection or prerequisites.

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/hydroCoderClaud/mcpHydroSSH'

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