Skip to main content
Glama
MCP Dokploy Online
by igoruam

security-delete

Destructive

Delete a security configuration from Dokploy by its security ID, removing the associated access or authentication settings from your project.

Instructions

POST /security.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": {
      "securityId": "<securityId>"
    },
    "name": "security-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
securityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 profile is known without the description. The description adds nothing further: it does not say whether the deletion is permanent, whether dependent resources or credentials are revoked, whether confirmation is required, or what the response contains. It does not contradict the annotations, but it contributes zero behavioral context.

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?

The text is short, but brevity here is under-specification rather than concision; there is no front-loaded purpose statement, just a route fragment. Nothing is wasted because nothing is said.

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 required parameter and no output schema, the description should carry the full burden of explaining permanence, side effects, and identifier semantics. It provides none of that, making the definition insufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter securityId has 0% schema description coverage, so the schema says only that it is a non-empty string. The description does not compensate at all: it does not explain what identifier this is, where to obtain it, or whether it can reference another entity's ID. Only the parameter's name hints at meaning.

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 /security.delete" restates the tool name and HTTP verb without saying what a security object is or what deleting it entails. An agent can infer a destructive delete of a security resource by combining the name and the route, but the description itself adds no specificity beyond the identifier.

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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer a sibling such as security-update or server-security. The definition is a bare endpoint string, leaving routing entirely to the agent's guesswork.

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