Skip to main content
Glama
MCP Dokploy Online
by igoruam

libsql-saveEnvironment

Idempotent

Saves environment variables for a LibSQL database instance in Dokploy by updating its configuration with the provided environment string using the LibSQL ID.

Instructions

POST /libsql.saveEnvironment

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>",
      "env": "<env>"
    },
    "name": "libsql-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
libsqlIdYes

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 supply idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds only the POST verb, giving no information about what is overwritten, whether existing env values are replaced or merged, or what permissions are needed.

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 that brevity comes from under-specification rather than economy. The single route string carries no front-loadable meaning for an agent.

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-parameter required mutation with no output schema and no parameter documentation anywhere, the definition is essentially empty. Everything an agent needs to invoke it correctly is missing.

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 are required, schema description coverage is 0%, and the description says nothing about them. An agent cannot tell from any source whether `env` is a raw env-file string, a JSON blob, or a single variable 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 only restates the tool name as an HTTP route ("POST /libsql.saveEnvironment"). The POST verb implies a mutation and the name implies libsql environment scope, but no verb+resource statement explains what is actually saved or how it differs from siblings like mysql-saveEnvironment or environment-update.

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 alternatives such as environment-update or the parallel per-database saveEnvironment tools. An agent has nothing to route on.

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