Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-readLogs

Read-onlyIdempotent

Retrieve and filter Redis service logs from a Dokploy instance. Limit results by tail count, time window, or search text to inspect errors and troubleshoot deployments.

Instructions

GET /redis.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": {
      "redisId": "<redisId>"
    },
    "name": "redis-readLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
redisIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond that — no note on how logs are fetched, whether tail is applied after or before filtering, or what a 'since' window means in practice. It does not contradict the annotations, but it is empty of behavioral context.

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 certainly short, but the brevity is under-specification rather than efficiency — a single endpoint string with no front-loaded statement of purpose or constraints. Nothing is wasted because nothing is said.

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?

For a four-parameter tool with filtering windows, a default line cap of 100 (max 10000), a regex-constrained time window, and no output schema, the definition is far too thin. An agent cannot determine how to page, how to bound results, or what the return shape looks like.

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?

Schema description coverage is 0% across four parameters, so the description carries the full burden and supplies nothing. The meaning of 'tail', 'since' (its 'all|Ns|Nm|Nh|Nd' pattern), 'search', and 'redisId' are all unexplained, including the interaction between 'since' and 'tail'.

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 HTTP endpoint 'GET /redis.readLogs', which restates the tool name rather than explaining what it does. An agent can infer log retrieval for a Redis instance from the name alone, but the description contributes no verb, scope, or outcome of its own.

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

Usage Guidelines1/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 when not to use it, and no reference to alternatives such as ai-analyzeLogs for interpretation or the per-service readLogs siblings. Everything about selection is left to the name.

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