Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-update

Idempotent

Update Dokploy user account details such as email, name, password, verification, and ban settings to keep access and profile information current.

Instructions

POST /user.update

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
emailNo
imageNo
bannedNo
lastNameNo
passwordNo
banReasonNo
createdAtNo
firstNameNo
updatedAtNo
banExpiresNo
createdAt2No
licenseKeyNo
isRegisteredNo
emailVerifiedNo
expirationDateNo
currentPasswordNo
serversQuantityNo
stripeCustomerIdNo
twoFactorEnabledNo
allowImpersonationNo
enablePaidFeaturesNo
stripeSubscriptionIdNo
enableEnterpriseFeaturesNo
sendInvoiceNotificationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations only supply openWorldHint and idempotentHint; the description adds nothing about what a partial update does, which sensitive fields (password, currentPassword, licenseKey, stripeCustomerId, allowImpersonation) are writable, or what permissions are needed. With 25 optional fields and no behavioral context, an agent cannot predict side effects.

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 the brevity comes from under-specification rather than efficiency; a bare HTTP route carries no front-loaded intent. There is no structure beyond method and path.

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?

A 25-parameter user-mutation tool with no output schema and no annotation coverage of destructive/safety semantics needs substantial description, yet nothing beyond the route is provided. Critical facts like which fields are privileged or irreversible are absent.

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?

All 25 parameters have 0% schema description coverage, and the description does not mention a single field or explain that zero required parameters means a partial/merge update. It does nothing to compensate for the large semantic gap.

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 route string "POST /user.update", which restates the tool name as an HTTP method and path. An agent can infer that it mutates a user record, but no verb/resource statement or distinction from siblings like user-one, user-assignPermissions, or user-remove is given.

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 guidance on when to use this tool versus the many other user-* siblings, no mention of prerequisites (admin scope, root access), and no note on update semantics. The route string implies usage but states nothing.

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