Skip to main content
Glama
Sign In
claude-ssh-mcp

claude-ssh-mcp

by MaraBank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ssh_remove_server

Remove a saved server from servers.json and disconnect it if currently active.

Instructions

Remove a saved server from servers.json and disconnect if currently active.

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": {
      "sessionName": "<sessionName>"
    },
    "name": "ssh_remove_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNameYesName of the server to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description fully explains the two behaviors: removal from servers.json and disconnection if active. This is explicit about the destructive action. Minor omissions: no mention of undo or error handling.

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?

Single sentence, front-loaded with verb and object, no unnecessary words. Highly concise and effective.

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 simple removal tool with one parameter and no output schema, the description covers core behavior. Missing are error cases, return value, and confirmation, but given low complexity, it is mostly complete.

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 description for sessionName is clear. The tool description adds no extra parameter context beyond the schema, so baseline of 3 is appropriate.

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' and the resource 'saved server from servers.json', and adds the disconnection behavior. It easily distinguishes from sibling tools like ssh_connect, ssh_disconnect, and ssh_list_sessions.

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?

No guidance on when to use this tool versus alternatives. It does not specify when not to use, prerequisites, or compare with ssh_disconnect or ssh_list_sessions.

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