Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupLibsql

Idempotent

Trigger an on-demand backup of a LibSQL database using its backup ID when scheduled backups are not enough.

Instructions

POST /backup.manualBackupLibsql

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": {
      "backupId": "<backupId>"
    },
    "name": "backup-manualBackupLibsql"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 safety profile is partly covered. The description adds nothing beyond the HTTP verb, leaving unstated whether the backup is synchronous or async, where artifacts land (relevant given the backup-listBackupFiles sibling), whether it affects the running libsql service, or what errors occur for an unknown backupId.

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 string is short, but its brevity is under-specification rather than conciseness: there is no front-loaded purpose statement, no structure, and the only content is an endpoint path that duplicates the tool 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?

A mutation-style trigger with a required, entirely undocumented parameter, no output schema, and only partial annotations needs far more description than a route path. Nothing tells the agent what a successful call produces or what constraints apply, so the definition is inadequate for correct invocation.

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 backupId has 0% schema description coverage, and the description says nothing about it. An agent cannot tell whether backupId names a pre-existing backup record, a target instance identifier, or a caller-supplied label for the new backup.

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 route string "POST /backup.manualBackupLibsql", which largely restates the tool name. It conveys no verb-plus-resource explanation such as 'triggers a manual backup of a Libsql instance', and gives no way to distinguish it from sibling backup-manualBackupMySql/Postgres/etc. beyond the name itself.

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 when-to-use guidance at all: nothing says whether this is the right tool before a libsql-remove, after libsql-create, or how it differs from backup-create or backup-manualBackupCompose. The only hint is the libsql fragment in the name, which the description neither confirms nor explains.

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