Skip to main content
Glama
Sign In
SSH MCP Server

SSH MCP Server

by tufantunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sftp-list

Read-only

List a remote directory over SFTP with a bounded entry count and response size, providing read-only directory listing.

Instructions

List a remote directory over SFTP, with a bounded number of entries and a bounded response size. Read-only.

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": {
      "remotePath": "<remotePath>"
    },
    "name": "sftp-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoProfile name
maxEntriesNoMax entries to return (default 200, hard cap 1000)
remotePathYesRemote directory to list. No leading or trailing whitespace, and no control, bidirectional or zero-width characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.11.0
    • changedInput schema / properties / remotePath / description
      Previous value: -"Remote directory to list"New value: +"Remote directory to list. No leading or trailing whitespace, and no control, bidirectional or zero-width characters."
  2. Addedv2.9.0

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already indicates no mutation, and the description reinforces this with 'Read-only.' It adds value beyond the annotation by disclosing bounded response size and bounded entry count, which are useful behavioral constraints an agent should know before invoking.

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?

One crisp sentence that front-loads the core operation, then adds the two most important behavioral constraints. No wasted words or repetition of schema details.

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?

For a simple list operation with one required parameter, full schema coverage, and a read-only annotation, the description is nearly complete. It lacks only an explicit statement of what the response contains (e.g., entry names/types), but the tool's purpose makes that reasonably inferable.

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 the schema already documents all parameters including maxEntries defaults and caps. The description's 'bounded number of entries' loosely echoes maxEntries, and 'bounded response size' adds a general constraint not tied to a specific parameter, but it does not meaningfully deepen parameter understanding.

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 states a specific verb and resource ('List a remote directory over SFTP') and adds distinguishing constraints: bounded number of entries and bounded response size. This is clearly distinct from sibling tools like sftp-upload/download or list-connections, even though it does not name them.

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 gives clear context for when the tool is appropriate: listing a remote directory. However, it offers no exclusions or guidance about when to prefer an alternative sibling tool, which would be helpful given the large sibling set.

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