Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-assignPermissions

Idempotent

Assigns or updates a Dokploy user's access permissions for projects, environments, services, servers, Git providers, and create/delete management actions.

Instructions

POST /user.assignPermissions

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": {
      "id": "<id>",
      "accessedProjects": "<accessedProjects>",
      "accessedEnvironments": "<accessedEnvironments>",
      "accessedServices": "<accessedServices>",
      "accessedGitProviders": "<accessedGitProviders>",
      "accessedServers": "<accessedServers>",
      "canCreateProjects": "<canCreateProjects>",
      "canCreateServices": "<canCreateServices>",
      "canDeleteProjects": "<canDeleteProjects>",
      "canDeleteServices": "<canDeleteServices>",
      "canAccessToDocker": "<canAccessToDocker>",
      "canAccessToTraefikFiles": "<canAccessToTraefikFiles>",
      "canAccessToAPI": "<canAccessToAPI>",
      "canAccessToSSHKeys": "<canAccessToSSHKeys>",
      "canAccessToGitProviders": "<canAccessToGitProviders>",
      "canDeleteEnvironments": "<canDeleteEnvironments>",
      "canCreateEnvironments": "<canCreateEnvironments>"
    },
    "name": "user-assignPermissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
canAccessToAPIYes
accessedServersYes
accessedProjectsYes
accessedServicesYes
canAccessToDockerYes
canCreateProjectsYes
canCreateServicesYes
canDeleteProjectsYes
canDeleteServicesYes
canAccessToSSHKeysYes
accessedEnvironmentsYes
accessedGitProvidersYes
canCreateEnvironmentsYes
canDeleteEnvironmentsYes
canAccessToGitProvidersYes
canAccessToTraefikFilesYes

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?

Annotations declare idempotentHint=true and openWorldHint=true, so the safety profile is partly covered, and "POST" is consistent with a write operation (no contradiction). However, the description adds nothing beyond that: it does not say whether existing permissions are overwritten, whether required permission entries must be complete, or what authorization is needed for a 17-field mutation.

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 under-specified rather than because it is efficient. There is no structure, no front-loaded purpose statement, and the single endpoint string does not earn its place as a description.

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 mutation tool with 17 required parameters, no output schema, and no parameter documentation, the description is completely inadequate. An agent has no basis to construct a valid call or anticipate side effects.

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 17 required parameters, and the description provides no meaning for any of them. The many boolean capability flags and ID array fields are left entirely undocumented, so an agent cannot know what values to supply.

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 raw endpoint string "POST /user.assignPermissions", which essentially restates the tool name rather than explaining what the tool does. It conveys a mutation of a user's permission set, but nothing about scope, effect, or how it differs from siblings such as user-getPermissions or user-update.

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, and no mention of alternatives like user-getPermissions for reading the current permission set. An agent must infer everything from the name alone.

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