Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

libsql-reload

Idempotent

Reload a libsql database instance by providing the database ID and app name.

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
libsqlIdYes
appNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.1

TDQS

D1.8/5.0
Behavior2/5

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

Annotations indicate idempotent and open world hints, but the description adds no behavioral context (e.g., what state changes occur, whether connections are reset, or if configuration is applied).

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 description is under-specified—single line lacks substance. Conciseness should not sacrifice meaning; here it provides nearly no useful information.

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?

Without output schema or parameter descriptions, the definition is incomplete for a potentially complex operation like database reloading. Sibling tools with similar naming patterns (e.g., mariadb-reload) suggest a consistent action, but no details confirm this.

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 has two required parameters (libsqlId, appName) with zero description coverage. The description does not explain their purpose or format, leaving the agent to infer.

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?

Description only says 'POST /libsql.reload', which is vague. It does not specify what reloading means for a libsql database, nor does it differentiate from sibling tools like libsql-rebuild or libsql-restart.

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?

No guidance on when to use this tool versus alternatives (e.g., libsql-rebuild, libsql-start, or other database reload tools). The description provides no context for selection.

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