Skip to main content
Glama
MCP Dokploy Online
by igoruam

customRole-remove

Destructive

Remove a custom role from Dokploy by role name to eliminate its assigned permissions and access scope.

Instructions

POST /customRole.remove

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": {
      "roleName": "<roleName>"
    },
    "name": "customRole-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNameYes

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 already declare destructiveHint=true and openWorldHint=true, but the description adds nothing beyond them, not even confirmation that this deletes a role. It does not disclose whether removal is reversible, what happens to members assigned to the role, or what the response contains.

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?

There is no wasted wording, but that is because there is almost no content at all; the endpoint string is not a substitute for a purpose statement and is not front-loaded with anything actionable.

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, irreversible-sounding mutation with an undocumented parameter and no output schema, the description covers none of the information an agent needs to invoke it safely.

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?

The single required parameter roleName has 0% schema description coverage, so the description needed to explain its format or constraints. It supplies no parameter meaning whatsoever, leaving the schema's bare type and minLength as the only guidance.

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 an HTTP method and path ("POST /customRole.remove"), which essentially restates the tool name customRole-remove. It implies deletion of a custom role but never states what is removed, from where, or how it differs from siblings like customRole-update or backup-remove.

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. An agent must guess that this deletes a custom role and has no signal about when removal is appropriate versus updating or listing roles.

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