Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-createUserWithCredentials

Create a new Dokploy user account with a specified email, password, and role for onboarding or access provisioning.

Instructions

POST /user.createUserWithCredentials

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": {
      "email": "<email>",
      "password": "<password>",
      "role": "<role>"
    },
    "name": "user-createUserWithCredentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYes
passwordYes

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?

The annotations expose only openWorldHint=true and a title, leaving the mutation semantics entirely to the description, which supplies nothing. It does not say whether the account is immediately active, whether a verification email is sent, whether the password is stored hashed, what errors occur on duplicate email, or what permissions the caller needs. The single implicit cue is the POST verb suggesting a write, which is not enough for a credential-creating 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?

The text is short but only because it is a raw route string, which is under-specification rather than conciseness. There is no front-loaded statement of effect, scope, or outcome to anchor the agent.

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 three-required-parameter mutation with no output schema and no meaningful annotations, the description should carry the full explanatory load and instead carries none. An agent has no basis to know what the call does beyond its name, what it costs, or what a success or failure looks like.

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 three required parameters (email, password, role), so the description must compensate and instead says nothing about any of them. It gives no meaning for 'role' (no enum or allowed values), no password policy beyond minLength 8, and no notion of whether email must be unique or is used for login.

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 the HTTP route 'POST /user.createUserWithCredentials', which restates the tool name rather than explaining what the tool actually does. It implies creating a user with credentials, but adds no verb-plus-resource explanation, no mention of what a 'credential' user is, and no differentiation from siblings like user-createApiKey or sso-showSignInWithSSO.

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., whether an admin or existing session is required), and no mention of alternatives such as inviting a user or creating an API key instead. The only signal is the tool name itself, which the agent must already interpret without help.

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