Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-move

Idempotent

Moves a LibSQL database to a specified Dokploy environment by ID, enabling relocation of the resource between deployment environments.

Instructions

POST /libsql.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "libsql-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes
targetEnvironmentIdYes

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 openWorldHint=true and idempotentHint=true, but the description adds nothing beyond that – no mention of downtime, data migration, reversibility, permission requirements, or whether the source environment is emptied. For a relocation operation that presumably mutates infrastructure, this is a serious disclosure gap.

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 this is under-specification rather than conciseness – the single endpoint string carries no explanation and no front-loaded intent.

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?

With two undocumented required parameters, no output schema, sparse annotations, and a multi-step infrastructure operation, the definition supplies none of the context an agent needs to call it safely or correctly.

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% and the description compensates for none of it: 'libsqlId' and 'targetEnvironmentId' are never explained, nor is whether the source environment is required to be running, empty, or distinct from the target.

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.move', which restates the tool name rather than explaining what moving a libsql resource entails or what it does to the resource. An agent cannot tell whether this relocates a database between environments, regions, or clusters.

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?

No guidance is given on when to use this tool, when not to, or how it differs from adjacent operations such as libsql-deploy, libsql-create, or the other *-move tools. The agent must infer prerequisites and alternatives entirely.

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