Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-deploy

Idempotent

Deploys a LibSQL database instance in Dokploy using the provided ID, enabling managed database provisioning through the MCP server.

Instructions

POST /libsql.deploy

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

Input Schema

NameRequiredDescriptionDefault
libsqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows the call is idempotent and reaches an external system. The description adds nothing beyond that: it does not say whether deployment recreates or mutates infrastructure, causes downtime, consumes resources, or requires the target to be stopped first.

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 short but that is under-specification rather than conciseness; a bare endpoint string is not a usable front-loaded summary. Nothing is front-loaded because there is essentially no content.

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 destructive-adjacent deploy mutation with one undocumented required parameter, no output schema, and no annotation coverage of side effects, the description should explain consequences and prerequisites. It supplies none of that, leaving the agent unable to call the tool with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter libsqlId has 0% schema description coverage, so the description carries the full burden and delivers nothing — it does not say whether this is an instance ID, an existing resource name, or where to obtain it. The route string implies an ID is posted but adds no meaning beyond the property 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 only the HTTP route "POST /libsql.deploy", which merely restates the tool name in endpoint form. It signals a deploy action on a libsql resource, but gives no scope, no indication of what deployment means, and no differentiation from siblings such as libsql-rebuild, libsql-start, or libsql-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 guidance at all — no prerequisites, no alternate-tool routing, and no exclusion criteria. An agent cannot tell from this text whether deploy applies to a new instance, an existing stopped instance, or a redeployment of existing configuration.

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