List the tables / collections / keys of a database on one of your servers — passwordless, over the same local-client path as data_query.
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Server id from hosts_list | |
| engine | No | Database engine on that server (default postgres) | |
| database | No | Database name (for sqlite: the .db file path) | |
| username | No | SSH login user (defaults to the tunnel's user, else root) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only, and the description adds meaningful behavioral context: the operation is passwordless and uses the same local-client path as data_query. This helps set accurate expectations about authentication and transport without contradicting the annotations.
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 front-loaded sentence with no filler. Every phrase earns its place: it names the operation, the resource, the transport, and the authentication 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 read-only listing tool with full schema coverage and annotations, the description covers the essential purpose, transport, and auth context. It does not describe the return shape, but 'List the tables / collections / keys' makes the result type reasonably self-evident, and there is no 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?
Schema description coverage is 100%, so the schema already documents all four parameters. The description's 'tables / collections / keys' phrasing adds light engine-awareness to the enum, but it does not add substantive per-parameter meaning beyond the schema.
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 clearly states the action ('List') and the resource ('tables / collections / keys of a database'), which is specific enough to distinguish it from query, file, and SSH operations. However, it does not explicitly name or contrast any sibling tool, so it stops short of the strongest differentiation.
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?
There is no explicit guidance on when to use this tool versus data_query or other siblings. The phrase 'same local-client path as data_query' signals a relationship but does not state a selection rule, alternatives, or exclusions.
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.