Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

docker_logs

Read-only

Retrieve Docker container logs from a remote Linux server and use the tail parameter to limit output to the last N lines for troubleshooting.

Instructions

Get logs from a Docker container. Use tail to limit number of lines.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>",
      "container": "<container>"
    },
    "name": "docker_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNo
serverYes
containerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing behavioral beyond that: it does not say whether logs are a one-shot snapshot or streamed/followed, whether output is truncated, what happens if the container is stopped, or how the remote server is reached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and with zero filler. It is efficient but so thin that the brevity reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter tool, the definition is still incomplete: with 0% schema coverage and no output schema, the description should clarify the required server and container semantics and the shape of the returned logs. As written, an agent has to guess at two required arguments before it can call the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It explains only one of three parameters (tail as a line limit), while the two required parameters, server and container, get no meaning beyond their bare titles — an agent cannot tell from either structured data or the description whether server is a hostname, alias, or ID, or whether container accepts a name or ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get logs from a Docker container" states a specific verb (get) and resource (logs from a Docker container), and the resource noun distinguishes it from siblings like docker_ps, docker_images, and docker_compose. It stops short of explicitly contrasting with any alternative, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says when to reach for this versus docker_compose or execute_command, no prerequisite that the container must exist/running, and no statement about the target server. The sentence "Use tail to limit number of lines" is parameter usage, not tool selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.