Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-saveEnvironment

Idempotent

Save environment variables for a MariaDB service in Dokploy to update its configuration and keep deployment settings current.

Instructions

POST /mariadb.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": {
      "mariadbId": "<mariadbId>",
      "env": "<env>"
    },
    "name": "mariadb-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
mariadbIdYes

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 state openWorldHint=true and idempotentHint=true, so the agent knows calls are safe to retry and touch external systems. The description adds nothing beyond the route — no mention of whether saving restarts the container, whether the env value replaces or merges, or what happens with a null env.

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 is under-specification rather than economy — a single route string carries no front-loaded statement of purpose. Nothing would be lost and much gained by a sentence or two.

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 mutation-style tool with two undocumented required parameters, no output schema, and no safety detail, the definition supplies none of the information an agent needs to invoke it correctly. It is effectively a name and an HTTP method.

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 description coverage is 0% across two required parameters (mariadbId, env), and the description provides no meaning for either. Notably, env is typed string-or-null and accepts free-form content, which the definition never explains.

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 /mariadb.saveEnvironment", which essentially restates the tool name plus a method. It gives no plain-language statement of what 'saving an environment' means for a MariaDB service (e.g. setting env vars and restarting), and offers nothing to distinguish it from mariadb-update or mariadb-deploy.

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, no prerequisites, and no mention of alternatives such as mariadb-update or the environment-* tools. Only the verb 'save' in the name hints at intent, which is the bare minimum.

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