Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-readLogs

Read-onlyIdempotent

Retrieve MySQL service logs from a Dokploy instance, with options to limit results by tail count or time window and filter by search text.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
mysqlIdYes

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 paging cost, whether the call blocks, or what the response contains - which leaves the openWorldHint (potentially slow / live container fetch) unexplained.

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 is under-specification rather than conciseness - a bare route string with no front-loaded statement of what the tool does. Nothing in it earns its place as documentation.

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 4-parameter tool with no output schema and zero parameter documentation, the description is completely inadequate. An agent has no basis to choose correct values for tail, since, or search, or to know what it receives back.

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?

Four parameters (mysqlId, tail, since, search) exist with 0% schema description coverage, and the description supplies no meaning at all. The regex/paging semantics of 'since' ('all' or 30s/5m/2h/1d) and the tail cap of 10000 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?

"GET /mysql.readLogs" merely restates the tool name as an HTTP route. It conveys no resource scope, log type, or distinction from the many sibling readLogs tools (mariadb-, postgres-, mongo-readLogs), so an agent cannot tell which backend or data it targets beyond the mysql prefix.

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 alternatives such as the ai-analyzeLogs tool that likely consumes this output, and no prerequisites. The 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