Lists Docker Compose stacks found in the stacks folder and reports whether each one is currently running.
List Compose stacks (one folder each under the stacks folder) and whether they are running.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
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 burden. It implies a read-only listing but never says so, and it omits whether results span all hosts or a single one, how errors are surfaced, or what 'running' derives from.
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?
One compact sentence with no waste, and the core resource is front-loaded. It is under-specified rather than verbose, so brevity is not the problem here.
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?
An output schema exists, so return values need not be explained. However, with no annotations and an undocumented host parameter, the description leaves meaningful gaps 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?
The single 'host' parameter has 0% schema description coverage and a default of empty string, and the description never mentions it. An agent cannot tell whether omitting it means all hosts, the local host, or an error.
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?
States a specific verb (list) and resource (Compose stacks) plus the additional signal of running state and the on-disk folder convention. It is reasonably distinguishable from docker_stack_status, though it never explicitly contrasts itself with that sibling.
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?
No guidance on when to use this versus docker_stack_status or docker_stack_config, and no mention of what 'host' means or when to supply it. The agent must infer everything from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.