Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-update

Idempotent

Update an existing LibSQL service's configuration in Dokploy, including resources, replicas, ports, environment variables, and Docker image settings.

Instructions

POST /libsql.update

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

Input Schema

NameRequiredDescriptionDefault
envNo
nameNo
appNameNo
commandNo
cpuLimitNo
libsqlIdYes
replicasNo
sqldNodeNo
createdAtNo
modeSwarmNo
networkIdsNo
descriptionNo
dockerImageNoghcr.io/tursodatabase/libsql-server:v0.24.32
labelsSwarmNo
memoryLimitNo
databaseUserNo
externalPortNo
networkSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
sqldPrimaryUrlNo
databasePasswordNo
enableNamespacesNo
externalGRPCPortNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
externalAdminPortNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
detachDokployNetworkNo
stopGracePeriodSwarmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/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 nothing about what a partial update does, whether omitted fields are preserved or reset, what permissions are required, or that this is a destructive-ish mutation of a running database service. It does not contradict the annotations, but it carries none of the behavioral burden a 35-parameter mutation tool needs.

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 only because it is under-specified rather than economical; there is no front-loaded purpose, no scope statement, and no structure at all. The HTTP route is the one piece of content and it duplicates the name.

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 tool with 35 parameters, nested swarm objects, and no output schema or parameter documentation, the definition supplies essentially nothing. An agent cannot safely construct a call from this description alone.

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 35 parameters, including nested swarm configs like placementSwarm, updateConfigSwarm, and restartPolicySwarm, plus enums for sqldNode and applicationStatus. The description compensates for none of this, leaving every parameter's meaning to be guessed from its 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?

The description is just "POST /libsql.update", which restates the tool name and HTTP verb without stating what an update actually changes. It gives no basis for distinguishing this from siblings like libsql-create, libsql-reload, libsql-rebuild, or libsql-deploy, all of which could plausibly modify a libsql instance.

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 when another tool (create, deploy, rebuild, changeStatus) would be the right choice instead. The agent must infer everything from the name.

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