Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mysql-saveEnvironment

Idempotent

Save environment variables to a MySQL database service on Dokploy to configure its runtime settings.

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
mysqlIdYes
envYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.1

TDQS

D1.3/5.0
Behavior2/5

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

Description adds no behavioral context. Annotations indicate idempotent and open world hints, but the description itself provides no additional transparency.

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?

Extremely short (one line) but under-specified. Under-specification is not conciseness; it lacks essential 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?

No output schema, minimal annotations, and description provides no context. Fails to give a complete picture of the tool's operation.

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 0% parameter description coverage. Description does not explain the meaning of mysqlId or env, leaving the agent to infer from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is just the HTTP method and endpoint, 'POST /mysql.saveEnvironment', which is a tautology. It does not state the tool's purpose: saving environment variables for a MySQL instance.

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?

No usage guidance provided. Description lacks any indication of when to use this tool vs alternatives like application-saveEnvironment or compose-saveEnvironment.

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