Skip to main content
Glama
Sign In
SSH MCP

SSH MCP

by mixelpixx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ssh_list_files

List files in a directory on a remote server via SSH connection. Specify connection ID and remote path to view directory contents.

Instructions

List files in a directory on the remote server

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": {
      "connectionId": "<connectionId>",
      "remotePath": "<remotePath>"
    },
    "name": "ssh_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesID of an active SSH connection
remotePathYesPath to the directory on the remote server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the action without revealing details like whether it lists recursively, includes file metadata, or how errors are handled. For a read operation, this is a notable gap.

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, tightly-worded sentence. It is concise, front-loaded, and free of unnecessary words.

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?

With no annotations and no output schema, the description should disclose what the tool returns (e.g., list of filenames, full paths, metadata) and any limitations. It does not. For a simple tool it is usable, but it leaves meaningful gaps.

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?

The input schema has 100% description coverage, so baseline is 3. The description does not add meaning beyond the schema—both remotePath and connectionId are adequately defined in the schema already.

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 tool's function: 'List files in a directory on the remote server' with a specific verb and resource. It distinguishes itself from siblings like ssh_read_file and ssh_download_file by focusing on listing directory contents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (when you need to list remote directory contents) but does not explicitly mention alternatives or exclusions. Since there are sibling tools, more explicit guidance would be better, but the basic context is present.

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