Skip to main content
Glama
MCP Dokploy Online
by igoruam

postgres-saveExternalPort

Idempotent

Configure or remove the external port for a PostgreSQL service in Dokploy by specifying its ID and the desired port.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
postgresIdYes
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 declare idempotentHint=true and openWorldHint=true but say nothing about destructive effects, permission requirements, or whether the container/instance restarts. The description adds zero context beyond the route — it does not even confirm that the port is persisted or what happens to the previous mapping. With no annotations covering the safety profile, this is a severe gap for a mutating configuration call.

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 brevity here reflects under-specification rather than efficient communication. A single route string with no front-loaded purpose statement gives the reader nothing to act on.

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-parameter mutating operation with no output schema, no parameter documentation, and only idempotency/open-world annotations, the description should carry the burden of explaining effect, scope, and failure modes. It supplies none of that, leaving the agent unable to call the tool safely without guessing.

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 both required parameters. The description does not clarify what postgresId refers to (name, UUID, internal id) or what an externalPort of null means (clear the mapping?) or what the valid port range is, so it fully fails to compensate for the undocumented schema.

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 /postgres.saveExternalPort", which merely restates the tool name in URL form. It never explains what saving an external port actually does for a Postgres instance (exposing it publicly, changing a mapping, persisting a setting) or how it differs from siblings like port-update or postgres-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 prerequisites, and no mention of alternatives such as port-update or port-create, which plausibly overlap with this operation. The agent must infer everything from the tool name alone.

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