Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-remove

Destructive

Deletes a specified libSQL database by ID from Dokploy, enabling cleanup of unused database instances.

Instructions

POST /libsql.remove

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

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds nothing beyond the route string. It does not disclose what state is destroyed, whether removal is reversible, whether dependent resources are affected, or what authorization is required for a destructive operation.

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 brevity here reflects under-specification rather than efficient communication. A bare HTTP route with no explanatory sentence does not front-load any actionable meaning.

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 destructive single-parameter mutation with no output schema and no parameter documentation, the description leaves everything an agent needs unknown. It fails to explain the effect, irreversibility, or how to supply the required identifier.

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?

The single parameter libsqlId has 0% schema description coverage, so the description must compensate, yet it says nothing about the parameter. An agent cannot tell from this text what a libsqlId is, where to obtain one, or what format it takes.

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 "POST /libsql.remove", which merely restates the tool name (libsql-remove) in URL form. It does not state in plain language what resource is deleted or what the operation accomplishes beyond the implied verb.

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 tool versus siblings such as libsql-stop, libsql-move, or other *-remove tools. No prerequisites, no exclusions, and no indication of what conditions warrant a destructive removal are provided.

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