Skip to main content
Glama
Sign In
SSH MCP Server

SSH MCP Server

by tufantunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reload-config

Destructive

Reports the SSH server's config load status or re-reads, validates, and applies the config file only when every check passes; refused reloads change nothing.

Instructions

Report or reload the server's config file. action="status" (the default) shows the config path, when it was loaded, the sha256 of its bytes and the result of the last reload; never the contents. action="reload" re-reads the file, validates it exactly as startup does, and applies it only if every check passes; a refused reload changes nothing. Command-line flags are never reloaded. Applying closes connections, with their sessions, whose profile was removed or whose connection fields changed, and clears approval grants.

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": "reload-config"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo"status" (default) reports the loaded config; "reload" re-reads and applies the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.21.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond destructiveHint by naming the concrete destructive effects: connections and their sessions are closed when a profile is removed or connection fields changed, and approval grants are cleared. It also discloses the fail-safe ('a refused reload changes nothing') and the privacy guarantee that status never returns config contents.

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?

Front-loaded with the two actions and dense with distinct facts; every sentence carries new behavior. Slightly long and unsegmented for a single paragraph, but there is no filler.

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?

With no output schema and a single-parameter surface, the description covers everything an agent needs: what status reports, what reload validates and applies, what happens on refusal, what is dropped on apply, and what is out of scope.

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?

Schema coverage is 100% and the enum is documented, so the baseline is 3. The description still adds meaning the schema lacks: which value is the default, what each mode actually returns or performs, and the contents-exposure caveat.

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?

States a specific verb set (report/reload) and resource (the server's config file), then splits into the two named actions with their exact effects. No sibling tool touches server config, so no confusion is possible.

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

Usage Guidelines5/5

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

Explicitly says action=status is the default, what each action is for, and states a key exclusion: command-line flags are never reloaded. An agent knows exactly which action to pick and what reload will not do.

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