Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-readLogs

Read-onlyIdempotent

Retrieve and filter PostgreSQL database logs from a Dokploy instance to troubleshoot errors, search messages, and control the number of recent log lines returned.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
postgresIdYes

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 structurally. The description adds nothing beyond that: no information on log retention window, pagination behavior, default time scope, or result volume caps implied by the tail maximum of 10000. With annotations carrying the safety signal, the remaining behavioral burden is unaddressed.

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?

The text is short but not concise in a useful sense; it is a single route token with no front-loaded statement of purpose. Under-specification, not verbosity, is the problem here.

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 tool with four parameters, zero schema descriptions, and no output schema, the definition should explain the parameters and expected return shape. Nothing is provided, so an agent cannot call it correctly without guessing at 'since' syntax and how 'tail' interacts with 'search'.

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 explanatory burden and provides none. The meaning of 'since' values like "all" or "7d", the interaction between 'tail' and 'since', and what 'search' matches are all left undocumented. The regex pattern hints at duration syntax but no semantics are stated.

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 route string "GET /postgres.readLogs", which restates the tool name in HTTP form rather than explaining what it does. It does not say what logs are read (server logs, container logs, query logs) or what the result represents. Sibling names like mariadb-readLogs imply a family pattern, but the definition itself contributes no differentiation beyond the postgres prefix.

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 alternatives such as ai-analyzeLogs or other readLogs variants, and no prerequisites. An agent must infer entirely from the name that this reads Postgres logs rather than analyzing them.

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