Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-saveExternalPort

Idempotent

Saves the external port for a specified MySQL database in Dokploy, letting you expose or update its external connection port without manual configuration.

Instructions

POST /mysql.saveExternalPort

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>",
      "externalPort": "<externalPort>"
    },
    "name": "mysql-saveExternalPort"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes
externalPortYes

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 only declare openWorldHint=true and idempotentHint=true; the description adds no behavioral context whatsoever. It does not disclose that this mutates the MySQL instance's exposed port, what happens on port conflicts, whether a restart is required, or what an error response looks like.

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 the brevity is under-specification rather than concision — the single route string carries no information an agent could act on. There is no front-loaded purpose statement or structure to speak of.

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-required-parameter mutation tool with no output schema and no readOnly/destructive annotations, the description is completely inadequate. Nothing an agent needs in order to invoke it correctly — effect, preconditions, or parameter meaning — 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, so the description must compensate and it does not. It gives no meaning for mysqlId (instance identifier format?) or externalPort (numeric port range, null semantics, collision rules), leaving both parameters entirely undocumented.

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 just the HTTP route 'POST /mysql.saveExternalPort', which restates the tool name in transport form rather than explaining what the operation does. It never says that an external (public) port is being assigned/bound to a MySQL instance, nor what distinguishes it from mysql-saveEnvironment or port-create.

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, when-not-to-use, or prerequisite information at all. The agent cannot tell from this text whether the call is needed before/after mysql-deploy, whether the port must exist first via port-create, or how it differs from the sibling saveExternalPort tools for other engines.

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