Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-readLogs

Read-onlyIdempotent

Read logs for a LibSQL instance in Dokploy, with filters for tail count, time range, and search text to diagnose issues.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tailNo
sinceNoall
searchNo
libsqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds nothing beyond them — no note on pagination of log output, ordering, retention window, or whether the call hits an external log store (relevant given openWorldHint). It does not contradict the annotations, but it also contributes no disclosure.

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 brevity here reflects under-specification rather than economy — the single route string has no front-loaded purpose, no verb-object statement, and no structure an agent can act on.

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, zero-coverage, mutation-free but externally-scoped read tool, the description provides none of what is needed: no parameter explanation, no log-scope statement, and no indication of result shape (there is no output schema to fall back on).

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 carries the full burden for four parameters (tail, since, search, libsqlId). It explains none of them: the meaning of tail's default 100, the 'all' vs '30m'-style since syntax, or the scope of search is 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 restates the HTTP route ("GET /libsql.readLogs") rather than explaining the tool. It conveys only that logs are read for a libsql resource, with no statement of what log content, scope, or format is returned, and nothing distinguishes it from sibling tools such as postgres-readLogs or libsql-one.

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 prerequisites, and no mention of any alternative. The agent must infer from the name alone that this retrieves logs rather than, say, configuration or status.

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