Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-rebuild

Idempotent

Rebuild a LibSQL database instance by ID to refresh its deployment and configuration through Dokploy.

Instructions

POST /libsql.rebuild

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

Input Schema

NameRequiredDescriptionDefault
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 declare idempotentHint=true and openWorldHint=true but omit destructiveHint/readOnlyHint, so the description must carry the safety burden. A rebuild of a database service plausibly destroys or resets the instance, and the description discloses nothing about data loss, downtime, permissions, or return behavior.

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 brief and front-loaded, but the brevity is under-specification rather than conciseness: an HTTP route fragment is not a substitute for a purpose statement. Nothing here helps the agent decide or act.

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 potentially destructive lifecycle operation on a database with no output schema and no documented parameters, the definition is completely inadequate. An agent would have to infer the operation's semantics entirely from the name.

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 required parameter libsqlId has 0% schema description coverage, so the description must explain its meaning and accepted format. It says nothing, leaving the agent with no idea how to identify the target instance (ID prefix, UUID, name?).

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?

"POST /libsql.rebuild" only restates the tool name plus an HTTP verb. It never says what 'rebuild' means for a libSQL instance — re-provision the container, rebuild an image, recreate from backup, or reset data. Siblings like libsql-reload, libsql-deploy, and libsql-start make the distinction even more necessary, and none is addressed.

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 such as libsql-reload or libsql-stop/start. The agent must guess whether rebuild is safe to use instead of those 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