Skip to main content
Glama

compose_logs

Read-only

Fetch a bounded slice of logs from a Docker Compose project without following. Supports filtering by service, tail, since, until, timestamps, and returns returncode/stderr on failure.

Instructions

Fetch a bounded slice of logs from a compose project (never follows).

Bounded and non-following by design, so it always returns promptly. For one container's logs use container_logs; for a swarm service use service_logs. Log text arrives on stdout. Does not raise on a non-zero CLI exit — inspect returncode/stderr in the result.

args: project_dir - Dir with the compose file (default: server cwd; copied to the target host if no local plugin) files - Explicit compose file paths (repeatable, -f) project_name - Compose project name override services - Restrict to these services (default: all) tail - Lines per container (default 200), or the literal "all" (still capped at MAX_CLI_OUTPUT_BYTES) since - Show logs since this timestamp/duration (e.g. "10m", "2024-01-01T00:00:00") until - Show logs before this timestamp/duration timestamps - Include per-line timestamps returns: dict - {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tailNo
filesNo
sinceNo
untilNo
servicesNo
timestampsNo
project_dirNo
project_nameNo
Behavior5/5

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

Annotations only declare readOnlyHint=true and destructiveHint=false. The description adds crucial behavior: 'never follows', 'always returns promptly', 'Log text arrives on stdout', and especially 'Does not raise on a non-zero CLI exit — inspect returncode/stderr in the result.' This goes well beyond annotation hints and helps the agent interpret results correctly.

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

Conciseness5/5

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

The description is well-structured: a leading summary paragraph front-loads the core behavior, followed by a compact arg list. Every sentence adds value—no filler. The parameter explanations are grouped logically and remain scannable despite covering 8 parameters.

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

Completeness5/5

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

The tool has 8 parameters, no output schema, and 0% schema description coverage, so the description must carry full weight. It does: it covers all params, return values (dict with returncode/stdout/stderr/truncated), failure behavior (non-zero exit not raising), and placement among siblings. This is fully adequate for an agent to select and invoke correctly.

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

Parameters5/5

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

Although schema description coverage is 0%, the description includes an 'args' block that explains every parameter with concrete meaning: 'project_dir - Dir with the compose file...', 'services - Restrict to these services...', 'tail - Lines per container (default 200), or the literal "all"...', etc. This fully compensates for the bare schema and supplies format hints for `since`/`until`.

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 opens with a specific verb+resource: 'Fetch a bounded slice of logs from a compose project (never follows).' It clearly distinguishes from sibling tools by name-checking `container_logs` and `service_logs` for other log sources, and the 'never follows' qualifier adds precision.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'For one container's logs use `container_logs`; for a swarm service use `service_logs`.' It also explains when this tool is appropriate ('bounded and non-following by design, so it always returns promptly'), giving the agent clear decision criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/L337-org/docker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server