Skip to main content
Glama
MCP Dokploy Online
by igoruam

port-create

Creates a port mapping for a Dokploy application, binding a published port to a target port with optional TCP/UDP protocol and ingress or host publish mode.

Instructions

POST /port.create

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": {
      "publishedPort": "<publishedPort>",
      "targetPort": "<targetPort>",
      "applicationId": "<applicationId>"
    },
    "name": "port-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolNotcp
targetPortYes
publishModeNoingress
applicationIdYes
publishedPortYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and a title, so the description carries the full disclosure burden for a mutating tool and delivers none of it: no statement that a mapping is created/persisted, no conflict handling for an already-published port, no permission or scope requirements, and no note that the effect is on a live deployment.

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 a single endpoint token with no wasted words, but this is under-specification rather than conciseness — there is no front-loaded statement of what the call does or what it requires.

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 five-parameter, three-required mutating tool with no output schema and only a generic openWorldHint annotation, the description says nothing an agent needs in order to invoke it correctly. Every meaningful detail must be inferred from parameter names alone.

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 five parameters, and the description provides no meaning for publishedPort vs targetPort, nor any hint about how protocol and publishMode default values affect behavior. The enums in the schema are the only self-documentation available, and the description compensates for none of the gap.

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?

"POST /port.create" restates the tool name and HTTP method without describing the resource or effect in domain terms — it does not say it creates a port mapping for an application. An agent can guess at intent from the name, but the description itself adds no verb+resource explanation and nothing distinguishes it from port-update or port-delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 (e.g., an existing applicationId), and no mention of alternatives such as port-update for modifying an existing mapping. The only signal is the HTTP verb, which the agent must interpret on its own.

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