Skip to main content
Glama
ssh-mcp-pro

ssh-mcp-pro

by oaslananka

Explain SSH Policy

ssh_policy_explain
Read-onlyIdempotent

Explain whether a requested SSH inspection, command, file access, or mutation would be allowed under policy without executing it or opening tunnels.

Instructions

Use this when ChatGPT or Claude needs to explain whether a requested SSH inspection or mutation would be allowed. This is explain-only and does not execute commands or open tunnels.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ssh_policy_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional remote path to evaluate in explain mode
actionNoRequested action class to evaluate without executing it
commandNoOptional command to evaluate in explain mode
hostAliasNoConfigured SSH host alias

Output Schema

NameRequiredDescriptionDefault
decisionYes
executedYes
toolProfileYes
requiresExplicitUserConfirmationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.12
    • changedOutput schema / properties / toolProfile / enum
      Previous value: -[
      -  "full",
      -  "remote-safe",
      -  "chatgpt",
      -  "claude",
      -  "remote-readonly",
      -  "remote-broker"
      -]New value: +[
      +  "full",
      +  "remote-safe",
      +  "chatgpt",
      +  "claude",
      +  "gemini",
      +  "remote-readonly",
      +  "remote-broker"
      +]
  2. First observedv1.1.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds meaningful context that is not obvious from them: this tool does not execute commands or open tunnels, which is a real ambiguity for an SSH-named tool. It stops short of describing how the policy result is reported, though an output schema covers that.

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?

Two short sentences, zero filler, with the usage trigger front-loaded and the no-side-effects constraint immediately following. Nothing could be removed without losing information.

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 an output schema present and full schema coverage, the description does not need to explain return values or parameter formats. A minor gap is that all four parameters are optional, and the description does not say what an invocation with no arguments evaluates.

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%, so every parameter (path, action, command, hostAlias) is already documented with its own description and the action enum is enumerated. The description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource: it evaluates whether a requested SSH inspection or mutation would be allowed, and explicitly frames itself as explain-only. This clearly separates it from execution-oriented siblings, though it does not name a specific alternative such as ssh_mutation_plan.

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?

"Use this when ChatGPT or Claude needs to explain whether a requested SSH inspection or mutation would be allowed" gives a concrete triggering context. It lacks explicit when-not conditions or a named alternative for the case where the agent actually wants to perform the mutation rather than explain it.

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