Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-saveExternalPort

Idempotent

Sets or clears the external port for a MariaDB database in Dokploy, enabling control over externally exposed database access.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes
externalPortYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true but say nothing about destructiveness or permissions, so the description carries real weight and delivers none of it. It does not disclose whether changing the port disrupts a running database, whether the port must be free, or whether the change is reversible; only the word "POST" hints at a mutation.

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 discipline. A single verbatim HTTP path conveys no front-loaded intent, and no sentence earns its place because the only content is transport metadata.

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?

This is a mutating, open-world operation on a stateful database service with two undocumented required parameters and no output schema. Everything an agent would need to call it safely and correctly is absent.

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% and both required parameters (mariadbId, externalPort) are bare typed fields. The description adds no meaning: not the ID format, not the valid port range, not whether null is permitted for externalPort or what null would mean.

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 raw route string "POST /mariadb.saveExternalPort", which restates the tool name rather than explaining the operation. It never says what an external port is, whether it exposes the database to the host/internet, or how this differs from siblings like port-create or mariadb-update.

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 prerequisite conditions, and no mention of any alternative tool. An agent cannot tell from this text whether to call this versus port-create, port-update, or mariadb-deploy.

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