Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-start

Idempotent

Starts a LibSQL database instance by ID in Dokploy, bringing the service online for applications and deployments that depend on it.

Instructions

POST /libsql.start

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

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 already declare idempotentHint=true and openWorldHint=true, but the description adds no behavioral context at all: it does not say what state the instance transitions to, whether data or configuration is preserved, how long startup takes, or whether the call can fail if the instance is already running.

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 not verbose, but this is under-specification rather than conciseness: a bare route string carries no usable information and is not front-loaded with purpose, preconditions, or effects.

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?

This is a state-mutating lifecycle operation with no annotations covering safety, no output schema, and a completely undocumented parameter, yet the description supplies none of the missing context an agent would need to invoke it correctly or predict its effect.

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 needed to explain its format and meaning and does not. Neither the identifier's expected form nor whether it is a UUID, slug, or numeric ID is stated anywhere.

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.start", which restates the tool name rather than explaining what starting a libSQL instance entails. An agent can guess it initiates a previously stopped instance, but that comes from the name, not the description, and there is no differentiation from siblings like libsql-deploy or libsql-rebuild.

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 prerequisite state described (e.g. that the instance must be stopped or that stop is the inverse operation via libsql-stop), and no conditions for choosing this over libsql-deploy or libsql-reload.

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