Lists Docker containers on a remote SSH host with name, image, and status, including stopped ones by default and optional case-insensitive regex filtering.
List containers on a host as name, image, status (tab separated).
| Name | Required | Description | Default |
|---|---|---|---|
| all | No | Include stopped containers | |
| host | Yes | ||
| filter | No | Case-insensitive regex on the line |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the tab-separated output format, but does not mention permissions, read-only nature, error behavior, or how host connectivity is handled.
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?
A single, front-loaded sentence that states the action, resource, and output shape with no wasted words.
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 read-only listing tool, the description covers the output columns but leaves the required host parameter ambiguous and does not explain defaults or filtering behavior. It is minimally adequate but misses important context for correct invocation.
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 coverage is 67%, but the required 'host' parameter has no description in either the schema or the description. The description adds output formatting but does not clarify what 'host' expects, nor does it explain how 'filter' interacts with the returned line format.
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 containers on a host') and specifies the returned fields. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like docker_logs or docker_exec.
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 guidance on when to use this tool versus alternatives such as docker_logs or docker_exec. The default behavior of including stopped containers is only visible in the schema, not explained in usage terms.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.