Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-create

Creates a LibSQL database instance in Dokploy with the specified server, environment, primary or replica node role, namespace setting, and credentials.

Instructions

POST /libsql.create

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": {
      "name": "<name>",
      "appName": "<appName>",
      "environmentId": "<environmentId>",
      "description": "<description>",
      "databaseUser": "<databaseUser>",
      "databasePassword": "<databasePassword>",
      "sqldNode": "<sqldNode>",
      "sqldPrimaryUrl": "<sqldPrimaryUrl>",
      "serverId": "<serverId>"
    },
    "name": "libsql-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameYes
serverIdYes
sqldNodeYes
descriptionYes
dockerImageNoghcr.io/tursodatabase/libsql-server:v0.24.32
databaseUserYes
environmentIdYes
sqldPrimaryUrlYes
databasePasswordYes
enableNamespacesNo

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 supply only openWorldHint=true and say nothing about mutation semantics, so the description carries the full burden. It discloses nothing about side effects, credentials required, whether a running instance is provisioned, or what happens on partial failure during creation — a serious gap for a 9-required-parameter write 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?

It is short, but that brevity is under-specification rather than efficiency — a single route fragment with no front-loaded statement of purpose. Nothing in the sentence earns its place beyond echoing the title.

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?

A 9-required-parameter provisioning tool with no output schema and no annotation coverage needs the description to explain intent, effects, and parameter meaning. The one-line endpoint reference supplies none of that.

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% across 11 parameters, and the description adds no meaning to any of them. Critical ambiguities are unaddressed: the primary/replica enum for sqldNode, the relationship between sqldPrimaryUrl and serverId, the default dockerImage, and whether enableNamespaces changes downstream behavior.

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.create" merely restates the tool name and an HTTP method; it never says what is actually created (a libSQL database instance?) or what the result is. It gives an agent no basis to distinguish this from siblings such as libsql-deploy, libsql-start, or mariadb-create.

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, when-not-to-use, or prerequisite guidance of any kind. The description does not mention that this is the provisioning step preceding libsql-deploy or libsql-start, leaving the ordering entirely to inference.

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