List the servers reachable through Termalin (your tunnel agents). Returns id, name, whether the server is online, and the default login user. Use the id with ssh_exec.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already ask readOnlyHint=true, so the read-only nature is covered. The description adds useful behavioral detail about what the tool returns and scopes the result set to Termalin reachable servers, which goes beyond the annotation.
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?
Two concise sentences with no filler. The first sentence states the purpose, the second states the output and gives the follow-up usage. Every sentence carries essential information.
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?
Given no parameters, no output schema, and a low-complexity listing, the description is functionally complete enough: it covers purpose, scope, output fields, and the next command. Offline reachability and sorting are minor omitted details, but no are not necessary.
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?
There are zero parameters and schema coverage is 100%, so no additional parameter explanation is needed. The description does enough by explaining that the returned id is the relevant value for following commands.
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 the action ('List') and the specific resource ('servers reachable through Termalin'), and even enumerates the returned fields (id, name, online status, default login user). It also positions the tool within its sibling set by referencing ssh_exec, so an agent can clearly distinguish it from sftp or password tools.
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 a clear context: use it to discover servers reachable through the current tunnel agents and obtain the id needed for ssh_exec. It does not explicitly compare it to sftp_list or other alternatives, but the framing is clear enough.
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.