Skip to main content
Glama
MCP Dokploy Online
by igoruam

port-delete

Destructive

Deletes a port configuration from a Dokploy service by its port ID, removing the specified port mapping.

Instructions

POST /port.delete

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": {
      "portId": "<portId>"
    },
    "name": "port-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
portIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the destructive nature is covered structurally. The description adds nothing beyond that — it does not say whether the port must be stopped first, whether attached domains or services are affected, or whether the deletion is reversible, which are exactly the gaps annotations cannot fill for a destructive operation.

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 economy — the single endpoint string carries no explanatory content and gives the agent nothing front-loaded 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 destructive, open-world mutation with an undocumented identifier parameter and no output schema, the definition provides no information about effects, preconditions, or results. It is completely inadequate relative to the tool's complexity and risk.

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 the single required parameter portId, so the burden falls entirely on the description, which says nothing about identifier format, where to obtain it, or whether it refers to an internal or external port record.

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 text "POST /port.delete" is a restatement of the tool name and title rather than a description of what the tool does. An agent can infer deletion of a port only by decoding the endpoint string, and nothing distinguishes it from siblings such as port-update or port-one.

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, and no mention of the existence of alternatives like port-update (to modify) or port-one (to inspect before deleting). The only implicit signal is the word 'delete'.

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