Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-remove

Destructive

Removes a Dokploy user by userId, revoking access and cleaning up accounts.

Instructions

POST /user.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": {
      "userId": "<userId>"
    },
    "name": "user-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes

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 destructiveHint=true and openWorldHint=true, so the risk profile is partly known, but the description adds nothing beyond that. It does not state irreversibility, what data is destroyed alongside the user, or any auth requirements — exactly the context a destructive tool needs.

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 extremely short with no wasted words, but this is under-specification rather than conciseness — the entire content is a route string that adds no information an agent cannot get from the name.

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 user-removal endpoint with no output schema and an undocumented required parameter, the definition supplies essentially nothing. An agent cannot confidently or safely invoke this tool on the basis of the description 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?

The single parameter userId has 0% schema description coverage, so the schema carries no semantics, and the description never mentions it. No format, identifier source, or constraint is supplied anywhere.

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 /user.remove" restates the tool name as an HTTP route rather than describing the operation. It conveys only that a user is removed and nothing about what removal means (hard delete vs. deactivation, cascade effects, scope).

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 alternatives named among the many sibling user tools (user-update, user-revokeSession, customRole-remove), and no prerequisites such as required permissions. An agent has no basis to choose this over a sibling.

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