Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-reload

Idempotent

Reload a LibSQL database instance for a specified app using its libsql ID and app name to apply configuration changes without redeploying the app.

Instructions

POST /libsql.reload

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>",
      "appName": "<appName>"
    },
    "name": "libsql-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
libsqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations only declare idempotentHint=true and openWorldHint=true; they say nothing about whether this restarts the instance, whether it causes downtime, or whether in-flight connections are dropped. A reload is potentially disruptive, yet the description discloses no behavior, side effects, or permission requirements at all.

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 short due to under-specification rather than efficiency; a bare HTTP route string is not useful front-loaded information for an agent choosing a tool.

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 two-required-parameter operation with no output schema and no safety annotations, the description should carry the entire explanatory load, and it carries none — no outcome, no return behavior, no disruption warnings.

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?

Both parameters (libsqlId, appName) are mutually required with 0% schema description coverage, and the description adds no meaning — not even which instance namespace appName refers to or the accepted identifier formats. With such low coverage the description should compensate and it does not.

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.reload", which essentially restates the tool name rather than explaining what a reload of a libsql instance actually does. It does identify the resource and that the call is a write-style POST, but gives no operational meaning beyond the identifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to reload versus any of the many adjacent operations (libsql-start, libsql-stop, libsql-rebuild, libsql-deploy, libsql-update, or the sibling application/mariadb/mysql reloads). No context, prerequisites, or exclusions are provided.

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