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

ssh_update_host

Destructive

Update SSH host fields with optimistic version checks to prevent stale writes; null clears jump-host or private-key paths, and identity changes clear saved login/sudo credentials.

Instructions

Update host fields with optimistic version checking. Null clears a jump host or private-key path. Connection identity changes clear saved login/sudo credentials to prevent reuse on a different endpoint; set credentials again. Existing connections require ssh_reset_connection. Rename preserves the ID.

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>",
      "patch": "<patch>"
    },
    "name": "ssh_update_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
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.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing the non-obvious side effects: connection identity changes wipe saved login/sudo credentials, null clears jump host or key path, renames preserve the ID, and stale versions produce conflicts.

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 a distinct fact (concurrency, null semantics, credential side effect, connection reset, rename behavior) 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, it covers semantics, side effects, and required follow-ups. It could mention how the updated host is returned or whether the patch is a merge, but nothing critical to invoking it safely is missing.

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?

With 67% schema coverage, the description fills the key gap by explaining that null for jumpHostId/privateKeyPath means 'clear' rather than 'leave unchanged' — a distinction the schema's anyOf null types do not convey. It leaves the remaining patch fields to the schema.

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 and resource ('Update host fields') plus the concurrency model ('optimistic version checking'), which distinguishes it from ssh_add_host and ssh_set_credentials without needing their schemas.

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?

Gives conditional guidance: existing connections require ssh_reset_connection, and credentials must be re-set via ssh_set_credentials after an identity change. It does not explicitly say when to choose add/delete instead, but the follow-up routing is clear.

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