View remote directory contents over SFTP, showing file names, types, sizes, and modification times. Use it to quickly inspect what's stored on a server without manual SSH.
List entries of a remote directory (name, type, size, mtime) via SFTP
| Name | Required | Description | Default |
|---|---|---|---|
| remotePath | Yes | Absolute POSIX directory path on the remote server, e.g. /var/log | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Changes observed during successful MCP inspections.
v1.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It does communicate that this is a list/read operation and what fields appear in the result, which is helpful. It doesn't mention behaviors like connection requirements, symlink handling, error conditions, or non-existent paths, but the core read-only nature is reasonably clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, tight sentence that front-loads the action and resource, then adds the useful output-field detail. There is no wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool, the description plus fully documented schema covers the essential context: what is listed, what fields are returned, and how the path/connection parameters behave. It lacks explicit return format details and error behavior, but those are minor given the simplicity and lack of an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters fully, including path format and the optional default for connectionName. The description adds no new parameter-level semantics, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('List'), a specific resource ('entries of a remote directory'), and the key returned attributes (name, type, size, mtime). It clearly distinguishes this tool from siblings like execute-command, upload, download, and list-servers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is implied by the description: when you need a directory listing over SFTP. However, there is no explicit guidance about when to prefer this over alternatives, no exclusions, and no mention of prerequisites such as needing a configured SSH connection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.