Fetch bounded stdout and stderr logs from a specific Docker container on a managed server. Read-only, returns JSON with log lines.
Tail one container's logs (stdout+stderr, bounded). Read-only. Returns JSON: {container, lines: [string]}.
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | Tail length (1-1000, default 200). | |
| container | Yes | Container name or ID. | |
| instance_id | Yes | Instance ID or name. |
Changes observed during successful MCP inspections.
v2.24.0v2.23.8v2.23.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. It declares read-only, bounded, and return format. Missing details like authentication requirements or behavior on missing container, but overall sufficiently transparent for a simple tail operation.
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 key information front-loaded: operation, scope, safety, and output format. No unnecessary 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?
Given lack of output schema, description includes return format. Parameters well-covered by schema. Could mention error handling or follow behavior, but sufficient for a bounded tail tool.
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 100% so description adds minimal value beyond parameter names and types. The description's mention of 'tail' aligns with the lines parameter but doesn't provide new semantic context.
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?
Description clearly states 'Tail one container's logs (stdout+stderr, bounded)' with specific verb and resource. Distinguishes from siblings like docker_ps (lists containers) and cloudwatch_get_log_events (AWS logs).
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?
Description indicates 'Read-only' usage safety and 'bounded' nature, but does not explicitly compare to alternatives like cloudwatch_get_log_events or docker_log_summary, which would help guide tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.