Skip to main content
Glama
samerfarida

MCP SSH Orchestrator

ssh_reload_config

Reload SSH configuration files to apply changes without restarting services, ensuring updated policies and security controls take effect immediately.

Instructions

Reload configuration files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for ssh_reload_config tool. Decorated with @mcp.tool() for registration in FastMCP. Calls config.reload() to reload configuration files from disk and returns success/error status.
    def ssh_reload_config(ctx: Context | None = None) -> ToolResult:
        """Reload configuration files."""
        try:
            config.reload()
            _ctx_log(ctx, "info", "ssh_reload_config", {"status": "reloaded"})
            return {"status": "reloaded"}
        except Exception as e:
            error_str = str(e)
            log_json({"level": "error", "msg": "reload_exception", "error": error_str})
            _ctx_log(
                ctx,
                "debug",
                "ssh_reload_config_error",
                {"error": sanitize_error(error_str)},
            )
            return {"status": "error", "error": sanitize_error(error_str)}
  • The Config.reload() helper method invoked by the tool handler. Loads the three YAML config files (servers.yml, credentials.yml, policy.yml) into the Config instance's _data.
    def reload(self) -> None:
        """Reload configuration from disk."""
        servers = _load_yaml(os.path.join(self.config_dir, "servers.yml"))
        creds = _load_yaml(os.path.join(self.config_dir, "credentials.yml"))
        policy = _load_yaml(os.path.join(self.config_dir, "policy.yml"))
        self._data = {"servers": servers, "credentials": creds, "policy": policy}
  • The @mcp.tool() decorator registers ssh_reload_config as an MCP tool, with auto-generated schema from type hints (optional ctx parameter).
    def ssh_reload_config(ctx: Context | None = None) -> ToolResult:
        """Reload configuration files."""
        try:
            config.reload()
            _ctx_log(ctx, "info", "ssh_reload_config", {"status": "reloaded"})
            return {"status": "reloaded"}
        except Exception as e:
            error_str = str(e)
            log_json({"level": "error", "msg": "reload_exception", "error": error_str})
            _ctx_log(
                ctx,
                "debug",
                "ssh_reload_config_error",
                {"error": sanitize_error(error_str)},
            )
            return {"status": "error", "error": sanitize_error(error_str)}
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('reload') but doesn't explain what this entails—e.g., whether it restarts services, applies changes without downtime, requires specific permissions, or has side effects like interrupting connections. For a tool that likely modifies system state, this lack of detail is a significant gap.

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 extremely concise—a single sentence with three words—and front-loaded with the core action. There is no wasted language or redundancy, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 tool's complexity (likely low, as it has no parameters) and the presence of an output schema (which should cover return values), the description is minimally adequate. However, it lacks context about the SSH system, behavioral details, and usage guidelines, which are important for a tool that reloads configurations. With no annotations and incomplete guidance, it meets only the bare minimum.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, as there are none to document. A baseline score of 4 is appropriate since no parameters exist, and the description doesn't attempt to describe any (which would be unnecessary).

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

Purpose3/5

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

The description states the action ('reload') and target ('configuration files'), which provides a basic purpose. However, it lacks specificity about what system or service these configuration files belong to (presumably SSH, inferred from the tool name), and doesn't distinguish this tool from potential alternatives like 'ssh_plan' or 'ssh_run' that might also involve configuration changes. This makes it vague but not tautological.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., after editing config files), exclusions (e.g., not for initial setup), or compare it to siblings like 'ssh_plan' (which might preview changes) or 'ssh_run' (which might apply configs). Without such context, users must infer usage from the tool name alone.

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/samerfarida/mcp-ssh-orchestrator'

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