Skip to main content
Glama
Sign In
sshand

sshand

by muradmalik23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ssh_remove_host

Destructive

Remove a host from the local SSH inventory permanently without affecting the remote server.

Instructions

Remove a host from the SSH inventory permanently.

This only removes the local config entry — it does NOT touch the remote server in any way.

Args: alias: The host alias to remove.

Returns: Confirmation or error message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "alias": "<alias>"
    },
    "name": "ssh_remove_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds value beyond annotations by clarifying that removal is permanent and local-only. This supplements the destructiveHint and readOnlyHint annotations effectively.

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 concise with three short paragraphs, each serving a purpose: main action, important caveat, and parameter/return info. No extraneous content.

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?

For a simple removal tool with one parameter and an output schema, the description covers the action, side effects, parameter meaning, and return value adequately.

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 description includes 'alias: The host alias to remove,' which adds meaning to the single required parameter. With 0% schema coverage, this is essential and well-provided.

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 clearly states the action ('Remove a host from the SSH inventory permanently') and the resource ('host'), distinguishing it from siblings like ssh_add_host or ssh_list_hosts.

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 explicitly notes that removal only affects the local config and does not touch the remote server, providing clear context on when to use the tool. No explicit alternatives are mentioned, but the scope is well-defined.

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