Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-readLogs

Read-onlyIdempotent

Read MongoDB logs for a Dokploy-managed database by ID, filtering by tail count, time window, or search term to troubleshoot issues.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
mongoIdYes

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, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on log retention, whether output streams or is bounded, or how the 'since'/'tail' windows interact with the underlying log buffer.

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 short, but that brevity comes from omission rather than efficiency. A bare route string is not front-loaded information an agent can act on; there is no structure to speak of.

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 four undocumented parameters, no output schema, and no explanation of return shape or limits (e.g., whether results are capped by tail), the definition is far too thin for the tool's complexity. An agent cannot call it correctly without guessing parameter meaning.

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%, so the description must compensate for all four parameters, yet it explains none of them. Critical semantics such as the 'since' pattern (all vs. 1h/30m), the tail cap of 10000, and 'search' filtering behavior are entirely undocumented.

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 route 'GET /mongo.readLogs', which effectively restates the tool name rather than explaining what reading logs means here (which logs, per-container, tailed vs. full). There is no verb-plus-resource statement an agent could use to distinguish this from siblings like mongo-one or mongo-search.

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 guidance on when to use this versus the many sibling *-readLogs tools or the ai-analyzeLogs alternative. The name implies log retrieval, but the definition provides no context, prerequisites, or exclusions to route an agent correctly.

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