Skip to main content
Glama
remote-ssh-mcp
by RuiFG

ssh_delete_host

Destructive

Deletes an SSH host and its stored credentials using the expected host version to prevent stale or conflicting removals.

Instructions

Delete a host and its credentials using expectedVersion. New operations in all clients fail afterward; already-started commands are not forcibly interrupted. Referenced jump hosts cannot be deleted. cleanupPending:true means credential cleanup must be retried by a later management operation.

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": {
      "hostId": "<hostId>",
      "expectedVersion": "<expectedVersion>"
    },
    "name": "ssh_delete_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostIdYesStable ID from ssh_list_hosts
expectedVersionYesCurrent host version from ssh_list_hosts; stale writes return HOST_CONFLICT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, yet the description goes further: it discloses the post-delete consequence that new operations fail in all clients, that in-flight commands are not interrupted, that jump-host references block deletion, and the meaning of cleanupPending:true requiring a later retry. This is exactly the kind of impact and follow-up information an agent needs before a destructive call.

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?

Four short sentences, each carrying distinct information (purpose, post-state, blocking condition, retry flag), with the core action front-loaded and no filler.

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?

For a destructive mutation with no output schema, the description covers the side effects, blocking preconditions, and even the cleanupPending response flag. Slightly short of perfect because it never states what the successful response contains or how idempotency/version mismatch recovery should proceed.

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%, and the schema already documents hostId, expectedVersion, and the HOST_CONFLICT stale-write behavior. The description only says 'using expectedVersion' without adding format or failure nuance beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Delete a host and its credentials') with a scoping detail tied to expectedVersion. It doesn't distinguish itself from siblings like ssh_forget_host_key or ssh_update_host, but the destructive scope is unambiguous.

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

Usage Guidelines3/5

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

Preconditions are given (must supply expectedVersion; referenced jump hosts cannot be deleted), which implies when the call is valid. However, there is no explicit routing guidance versus alternatives such as ssh_forget_host_key, and no statement of when a caller should prefer a different tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.