Skip to main content
Glama
simon-ami

Windows CLI MCP Server

delete_ssh_connection

Remove an SSH connection from the Windows CLI MCP Server by specifying its connection ID to manage secure remote access configurations.

Instructions

Delete an existing SSH connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesID of the SSH connection to delete

Implementation Reference

  • The deleteSSHConnection function implements the core logic to delete an SSH connection by ID from the configuration file by loading the config, removing the entry, and saving it back.
    /**
     * Delete an SSH connection.
     * @param connectionId The ID of the connection to delete.
     */
    const deleteSSHConnection = (connectionId: string): void => {
      const config = loadConfig();
      delete config.ssh.connections[connectionId];
      saveConfig(config);
    };
  • The input schema for the delete_ssh_connection tool, defining the required 'connectionId' string parameter.
    {
      name: "delete_ssh_connection",
      description: "Delete an existing SSH connection",
      inputSchema: {
        type: "object",
        properties: {
          connectionId: {
            type: "string",
            description: "ID of the SSH connection to delete"
          }
        },
        required: ["connectionId"]
      }
    },
  • src/index.ts:855-861 (registration)
    Registration and dispatch logic in the CallToolRequest handler's switch statement, which validates arguments and calls the deleteSSHConnection handler.
    case 'delete_ssh_connection': {
      const args = z.object({
        connectionId: z.string(),
      }).parse(request.params.arguments);
      deleteSSHConnection(args.connectionId);
      return { content: [{ type: 'text', text: 'SSH connection deleted successfully.' }] };
    }
  • src/index.ts:26-26 (registration)
    Import statement that brings the deleteSSHConnection handler into the main index module for use in tool dispatching.
    import { createSSHConnection, readSSHConnections, updateSSHConnection, deleteSSHConnection } from './utils/sshManager.js';
  • Export statement making deleteSSHConnection available for import by other modules.
    export { createSSHConnection, readSSHConnections, updateSSHConnection, deleteSSHConnection }; 
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a deletion operation but doesn't mention whether it's reversible, what permissions are required, what happens to associated resources, or error conditions. For a destructive operation with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple deletion tool and gets straight to the point without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'delete' entails (permanent removal? soft delete?), what gets returned, or error handling. Given the complexity of SSH connection management and lack of structured data, more context is needed.

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 description coverage is 100%, with the single parameter 'connectionId' fully documented in the schema. The description doesn't add any additional meaning about the parameter beyond what the schema already provides, so it meets the baseline for high schema coverage.

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?

The description clearly states the action ('Delete') and target resource ('an existing SSH connection'), providing specific verb+resource pairing. However, it doesn't differentiate this from sibling tools like 'ssh_disconnect' or 'update_ssh_connection', which might have overlapping functionality.

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 like 'ssh_disconnect' or 'update_ssh_connection', nor does it mention prerequisites (e.g., needing an existing connection ID). It simply states what the tool does without context for selection.

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/simon-ami/win-cli-mcp-server'

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