Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_setup_ssh

Idempotent

Set up SSH credentials for the current session by checking the SSH client, saving host/user with key/session/password, and testing connectivity.

Instructions

Mutating: saves SSH credentials to the process environment and config, and can open a real test connection. The action parameter (default "check") accepts check, save, test, skip. action=check is read-only: reports whether plink (Windows) or native ssh (macOS/Linux) was found, plus which of SSH_HOST, SSH_USER, SSH_PASS, SSH_KEY, SSH_SESSION are set. action=save requires host and user plus at least one auth source: key (a .ppk path, preferred), session (a saved PuTTY session name), or password (fed via stdin, never in the process list); missing pieces return status=incomplete. action=test runs the actual ssh command with a 15 second timeout and reports connected, failed, or error. Credentials last only for this session unless also set in system env or MCP client config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
hostNo
userNo
actionNocheck
sessionNo
passwordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.1
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"sassy_setup_sshOutput"New value: +"sassy_setup_sshDictOutput"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations include readOnlyHint=false, destructiveHint=false, but the description goes beyond by detailing that action=check is read-only, save mutates environment/config, test opens a real connection with timeout, and credentials are session-scoped. It also mentions password is via stdin for security. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded with the mutating nature and default action. It packs useful information per sentence without redundancy, though it is on the longer side. Good structure keeps key details up front.

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?

With 6 parameters, no required ones, and no enums, the description provides a detailed action breakdown and security notes. It mentions output statuses (incomplete, connected, failed, error) and session scoping, but does not mention the output schema details, which is acceptable since output schema exists.

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?

Schema description coverage is 0%, so the description must compensate. It explains the role of key, session, password, and action, but does not detail host/user beyond action=save requirements. The description adds significant meaning to action and auth source parameters, though host and user remain generic.

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 tool saves SSH credentials and can open a test connection, with specific actions. It distinguishes itself from setup_check_tools and setup_status by focusing on SSH setup, though it does not explicitly name those siblings.

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?

It provides clear context on when to use each action (check, save, test) and prerequisites (e.g., action=save requires host/user and auth source). It does not explicitly list alternatives or exclusions, but the action breakdown implies usage scenarios.

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