Retrieve recent Docker stack or service log lines, filtered by time and tail count, to inspect issues across an entire stack.
Show the last log lines of a whole stack, or one service of it. since like 10m, 2h, 2026-10-22.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | ||
| tail | No | ||
| since | No | ||
| stack | Yes | ||
| service | 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?
With no annotations, the description carries the full burden; 'Show' implies a read-only operation, which is helpful. However, it does not disclose default tail behavior, how 'host' targets a remote daemon, or any rate/size limits on the returned log volume.
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 short sentences, front-loaded with the core action, that earn their place by covering scope and time format. Minor grammatical awkwardness ('since like 10m') but no filler.
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. For a 5-parameter tool with zero schema descriptions, the missing meaning of 'tail' and 'host' leaves gaps an agent must guess at.
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 0% across 5 parameters, so the description must compensate. It only clarifies the 'since' format with examples ('10m, 2h, 2026-10-22') and the stack-vs-service relationship; 'tail' (default 100) and 'host' remain completely undocumented.
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 and resource ('Show the last log lines') and clarifies the scope choice between a whole stack and one service. It implicitly distinguishes itself from the sibling docker_logs (container-level) but never names that sibling explicitly.
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 phrase 'a whole stack, or one service of it' implies when the service parameter matters, but there is no explicit guidance on choosing this over docker_logs or docker_stack_status, and no prerequisites or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.