Skip to main content
Glama
simon-ami

Windows CLI MCP Server

update_ssh_connection

Modify SSH connection settings like host, port, username, password, or private key path for secure remote access to Windows systems through the Windows CLI MCP Server.

Instructions

Update an existing SSH connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdNoID of the SSH connection to update
connectionConfigNo

Implementation Reference

  • Core implementation of the update_ssh_connection tool logic: loads the server config, updates the specified SSH connection if it exists, and saves the config back to file.
    const updateSSHConnection = (connectionId: string, connectionConfig: any): void => {
      const config = loadConfig();
      if (config.ssh.connections[connectionId]) {
        config.ssh.connections[connectionId] = connectionConfig;
        saveConfig(config);
      }
    };
  • MCP tool dispatch handler for 'update_ssh_connection': parses and validates arguments using Zod schema, calls the updateSSHConnection helper function, and returns success response.
    case 'update_ssh_connection': {
      const args = z.object({
        connectionId: z.string(),
        connectionConfig: z.object({
          host: z.string(),
          port: z.number(),
          username: z.string(),
          password: z.string().optional(),
          privateKeyPath: z.string().optional(),
        })
      }).parse(request.params.arguments);
      updateSSHConnection(args.connectionId, args.connectionConfig);
      return { content: [{ type: 'text', text: 'SSH connection updated successfully.' }] };
  • Declarative input schema definition for the update_ssh_connection tool, used by MCP clients to validate tool calls.
    inputSchema: {
      type: "object",
      properties: {
        connectionId: {
          type: "string",
          description: "ID of the SSH connection to update"
        },
        connectionConfig: {
          type: "object",
          properties: {
            host: {
              type: "string",
              description: "Host of the SSH connection"
            },
            port: {
              type: "number",
              description: "Port of the SSH connection"
            },
            username: {
              type: "string",
              description: "Username for the SSH connection"
            },
            password: {
              type: "string",
              description: "Password for the SSH connection"
            },
            privateKeyPath: {
              type: "string",
              description: "Path to the private key for the SSH connection"
            }
          },
          required: ["connectionId", "connectionConfig"]
        }
      }
  • src/index.ts:471-509 (registration)
    Tool registration in the MCP ListTools response, including name, description, and input schema for update_ssh_connection.
    {
      name: "update_ssh_connection",
      description: "Update an existing SSH connection",
      inputSchema: {
        type: "object",
        properties: {
          connectionId: {
            type: "string",
            description: "ID of the SSH connection to update"
          },
          connectionConfig: {
            type: "object",
            properties: {
              host: {
                type: "string",
                description: "Host of the SSH connection"
              },
              port: {
                type: "number",
                description: "Port of the SSH connection"
              },
              username: {
                type: "string",
                description: "Username for the SSH connection"
              },
              password: {
                type: "string",
                description: "Password for the SSH connection"
              },
              privateKeyPath: {
                type: "string",
                description: "Path to the private key for the SSH connection"
              }
            },
            required: ["connectionId", "connectionConfig"]
          }
        }
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't disclose any behavioral traits like permission requirements, whether changes are reversible, what happens to unspecified fields, error conditions, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a basic tool description and is perfectly front-loaded with the essential information.

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 mutation tool with no annotations, no output schema, and incomplete parameter documentation (50% schema coverage), the description is insufficient. It doesn't address what the tool returns, error conditions, side effects, or provide enough context about the update operation. The description should do more to compensate for the lack of structured metadata.

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 50% (only 'connectionId' has a description in the schema, while 'connectionConfig' and its nested properties lack descriptions). The description adds no parameter semantics beyond what's implied by the tool name - it doesn't explain what fields can be updated, how to structure the config object, or provide examples. The baseline is 3 since the schema covers some parameters, but the description doesn't compensate for the coverage gap.

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 ('Update') and resource ('an existing SSH connection'), making the purpose immediately understandable. It distinguishes from 'create_ssh_connection' by specifying 'existing', but doesn't explicitly differentiate from other sibling tools like 'delete_ssh_connection' beyond the verb difference.

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. It doesn't mention prerequisites (e.g., needing an existing connection ID), when not to use it, or how it relates to sibling tools like 'create_ssh_connection' or 'delete_ssh_connection' beyond the basic verb difference.

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