Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-update

Idempotent

Update a MariaDB service in Dokploy by modifying its image, environment variables, resources, replicas, or database credentials. Use mariadbId to target the service.

Instructions

POST /mariadb.update

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>"
    },
    "name": "mariadb-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
nameNo
appNameNo
commandNo
cpuLimitNo
replicasNo
createdAtNo
mariadbIdYes
modeSwarmNo
networkIdsNo
descriptionNo
dockerImageNo
labelsSwarmNo
memoryLimitNo
databaseNameNo
databaseUserNo
externalPortNo
networkSwarmNo
ulimitsSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
databasePasswordNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
databaseRootPasswordNo
detachDokployNetworkNo
stopGracePeriodSwarmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true but omit readOnlyHint/destructiveHint. The description adds nothing: it doesn't say this is a mutation, whether it replaces or merges fields, whether omitted fields are reset, or whether the service restarts. For a 34-parameter update this is a severe gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a three-word HTTP path fragment. It is short but conveys no information, so there is nothing front-loaded and nothing that earns its place.

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 34-parameter mutation that rewrites service configuration needs substantial description, especially with no output schema and only minimal annotations. The definition provides none of what an agent needs to invoke it correctly.

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 34 parameters, and the description supplies no parameter information at all. Complex nested structures like modeSwarm, updateConfigSwarm, and placementSwarm are undocumented everywhere, leaving an agent unable to know their formats or meanings.

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 entire description is "POST /mariadb.update", which restates the tool name and HTTP method rather than describing what the tool does. It implies modifying a MariaDB service but gives no specifics about scope, fields, or effect.

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 when-to-use guidance, prerequisites, or alternatives are provided. With siblings like mariadb-changeStatus, mariadb-changePassword, mariadb-saveExternalPort, and mariadb-deploy, an agent cannot tell from this description which tool handles which kind of update.

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