Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-readLogs

Read-onlyIdempotent

Retrieve and filter MariaDB container logs from Dokploy to inspect recent output, search specific terms, or review entries from a chosen time window.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
mariadbIdYes

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, idempotentHint, and openWorldHint, so the safety profile is covered by structured data. The description contributes nothing beyond that — no mention of log source, ordering, truncation, or what the returned log stream looks like — but it does not contradict the annotations either.

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 that brevity comes from under-specification rather than tight writing. A bare route path is not front-loaded explanation and gives the agent no usable entry point.

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 parameters, one required, no output schema, and no annotations explaining semantics, the description needed to carry substantial weight and instead carries none. An agent cannot know what a call returns or how the filter parameters behave.

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, and the description says nothing about them. The meaning of 'tail' (line count?), 'since' (a duration like '2h' versus 'all'), and 'search' (substring? regex?) is left entirely undocumented, which is a serious gap for a filtering tool.

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 string "GET /mariadb.readLogs", which merely restates the tool name in URL form. It conveys the bare notion of reading logs for a MariaDB resource but adds no verb-level detail, scope, or differentiation from the many sibling *-readLogs tools.

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 guidance on when to use this tool, when not to, or how it relates to alternatives such as ai-analyzeLogs or the other per-service readLogs tools. An agent must infer everything from the name alone.

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