Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-one

Read-onlyIdempotent

Fetches a single LibSQL database by its ID from a Dokploy instance to inspect its configuration and status.

Instructions

GET /libsql.one

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-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes

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. The description contributes nothing beyond that: no mention of what is returned, whether a missing libsqlId errors, or whether the call requires authentication.

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 it is under-specified rather than concise. A route string alone does not earn its place as a tool description and leaves no front-loaded purpose statement.

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 that fetches a specific libsql instance by ID, an agent needs to know what is retrieved and what the identifier means. With no output schema and no annotation coverage of return shape, the description is wholly inadequate.

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?

There is one required parameter, libsqlId, with 0% schema description coverage, so the description must compensate and does not. It never explains what identifier format is expected or how it is resolved.

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 /libsql.one', which essentially restates the tool name plus a method. 'GET' weakly implies a read/retrieve of a libsql instance, but the description never says what resource is fetched or how it differs from the many libsql-* siblings such as libsql-readLogs or libsql-one-type detail operations.

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 alternatives. An agent cannot tell from the description when to call this versus libsql-changeStatus or other single-resource siblings.

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