List a directory on one of your servers over SFTP. Returns each entry's name, whether it's a directory, size and modified time. Runs keyless over Termalin's tunnel, like ssh_exec.
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Server id from hosts_list | |
| path | No | Directory to list (default the login home, ".") | |
| username | No | Login user (defaults to the tunnel's user, else root) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful behavioral context beyond the annotations: it runs keyless over Termalin's tunnel and returns name, directory flag, size, and modified time. The readOnlyHint annotation is consistent with the described read-only listing behavior.
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 two crisp sentences with no filler. It front-loads the core operation and then adds only the high-value details of return fields, keyless auth, and tunnel behavior.
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 listing tool with no output schema, the description covers the important return fields, the access mechanism, and the required server context. The schema covers all parameter semantics and defaults, making the overall definition sufficient without describing every edge case.
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?
Schema description coverage is 100%, so the schema already explains host, path, and username. The description adds no new parameter semantics beyond the general directory-listing context, which matches the baseline for fully documented schemas.
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 specific verb and resource: 'List a directory on one of your servers over SFTP.' It clearly distinguishes itself from sftp_read and sftp_write, which deal with file content rather than directory listings.
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 description gives clear context: use this tool to list SFTP directories on servers, and the returned entry fields indicate what an agent can expect. It does not explicitly name alternatives or say when not to use it, but the scope is clear enough for siblings like sftp_read and sftp_write.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool maps to a distinct action: password generation, host enumeration, SFTP file listing/reading/writing, and SSH command execution. Although sftp_read and ssh_exec could both be used to retrieve file contents, the descriptions explicitly separate them by file type and size.
Most tools follow a consistent <resource>_<verb> pattern: hosts_list, sftp_list, sftp_read, sftp_write, and ssh_exec. generate_password is the only outlier using <verb>_<noun>, but it is still clear, short, and doesn't cause real confusion.
Six tools is a tight, well-scoped set for managing remote servers via Termalin. Each tool covers a practical need without redundancy or feature bloat.
The main server-management workflow is covered: list hosts, execute commands, list files, read files, write files, and generate passwords. Minor gaps exist around SFTP operations like delete, move, rename, or create-directory, but these can be worked around with ssh_exec.