Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-saveExternalPort

Idempotent

Sets or clears the external port for a MongoDB service in Dokploy by MongoDB ID, so you can control how the database is exposed.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
mongoIdYes
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 already declare openWorldHint=true and idempotentHint=true, so the description needs only to add context such as what gets persisted, whether the Mongo container restarts, or whether existing mappings are overwritten. It adds none of that — the mutation semantics beyond the raw verb are undisclosed.

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 only because it carries no information beyond repeating the route. Nothing is front-loaded because there is nothing substantive to front-load.

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 mutation tool with two undocumented required parameters, no output schema, and only partial annotation coverage, the definition leaves the agent without enough to call it correctly or predict its effects.

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 the description says nothing about mongoId or externalPort. It does not clarify why externalPort is nullable, whether null clears the mapping, or what format the port takes, so the two required parameters are 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 only the HTTP route "POST /mongo.saveExternalPort", which restates the tool name rather than explaining what saving an external port does for a Mongo instance. An agent cannot tell from this whether it persists a port mapping, restarts the service, or returns anything.

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 guidance on when to call this versus siblings such as port-create, port-update, or mongo-saveEnvironment, nor any prerequisite or precondition mentioned. The route string alone gives no usage context.

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