Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-readLogs

Read-onlyIdempotent

Retrieve and filter logs for a specific Docker Compose container using compose and container IDs, with tail, time range, and search options. Troubleshoot deployments by inspecting service output.

Instructions

GET /compose.readLogs

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": {
      "composeId": "<composeId>",
      "containerId": "<containerId>"
    },
    "name": "compose-readLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
composeIdYes
containerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no indication of whether logs stream or are truncated, how far back 'since=all' reaches, or what happens when a container is stopped. It does not contradict the annotations.

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

Conciseness2/5

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

It is technically short, but the brevity is under-specification rather than conciseness; there is no front-loaded verb-plus-resource statement and no structure beyond an HTTP path fragment. Not a single informative sentence is present to trim.

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

Completeness1/5

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

With five undocumented parameters, no output schema, and no explanation of the return payload (log lines, timestamps, container metadata), the definition leaves an agent unable to construct a correct call beyond guessing from parameter names. A log-reading tool with filtering semantics needs far more than an endpoint path.

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

Parameters1/5

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

All five parameters (tail, since, search, composeId, containerId) have 0% schema description coverage, so the description carries the full burden — and it supplies no meaning for any of them. The regex pattern and defaults for since and tail are visible in the schema but unexplained, and the description never mentions filtering or tailing behavior.

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

Purpose2/5

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

The description is only the raw endpoint string "GET /compose.readLogs", which restates the tool name rather than explaining it. An agent can guess this retrieves container logs for a compose service, but nothing states scope, target resource, or how it differs from sibling log readers like application-readLogs or docker log tools.

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, no mention of prerequisites (a running container, a deployed compose project), and no pointer to alternatives such as ai-analyzeLogs for interpreting logs. The HTTP method alone hints it is a read, but selection guidance is absent.

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