Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-saveEnvironment

Idempotent

Saves the environment configuration for a specified MySQL service by ID, letting you update its environment variables through Dokploy.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
envYes
mysqlIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the description's job is to add mutation context — what gets overwritten, whether the service restarts, how secrets are handled — and it adds nothing. A bare route string leaves an agent with zero behavioral information beyond the annotations.

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 it is under-specified rather than concise: the single token is an internal route path that carries no user-facing meaning and is not front-loaded with any 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?

A two-parameter required mutation with no output schema, no parameter documentation, and no annotations describing side effects needs far more than an endpoint path. Nothing an agent needs to call this correctly is present.

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% for two required parameters (mysqlId, env), and the description supplies no meaning at all. It is not even clear whether `env` is a name, an environment identifier, or a blob of environment variables — a critical ambiguity for a save operation.

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 /mysql.saveEnvironment", which restates the tool name rather than explaining what saving an environment actually means for a MySQL service (persisting env vars? overwriting? restarting?). An agent can guess it mutates environment config, but gets no resource scope, no effect, and no differentiation from the many sibling *-saveEnvironment tools.

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 environment-create. The agent must infer entirely from the name whether saveEnvironment replaces or merges an existing environment.

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