Skip to main content
Glama
Sign In
MCP DevOps Kit

MCP DevOps Kit

by Jmfrodero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

docker_logs

Retrieve logs from a Docker container by specifying container ID or name, with options to limit line count or show last N lines.

Instructions

Get logs from a Docker container

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": {
      "container_id": "<container_id>"
    },
    "name": "docker_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
container_idYesContainer ID or name
linesNoNumber of lines to fetch (default 100)
tailNoShow last N lines (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must convey behavioral traits, but it only states the basic function. It does not disclose whether logs are streamed or fetched, the output format, error behavior, or permissions required.

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

Conciseness3/5

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

The description is very short (6 words), which is concise but overly minimal. It is not wasteful, but it sacrifices useful detail for brevity, making it only adequately structured.

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 tool with multiple parameters and no output schema, the description is incomplete. It lacks context on output format, behavior with different parameters, and error conditions, leaving the agent needing to infer from parameter descriptions alone.

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

Parameters3/5

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

The input schema already describes all three parameters with 100% coverage, so the description does not need to add details. However, it adds no additional meaning beyond the schema, meeting the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the action (Get) and the resource (logs from a Docker container). It distinguishes from sibling tools like docker_ps (list containers) and docker_stats (show stats), which have different purposes.

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?

No usage guidelines or context are provided. The description does not indicate when to use this tool versus alternatives like docker_ps or docker_stats, nor does it mention prerequisites or typical scenarios.

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

Deploy Server

Other Tools