Skip to main content
Glama
MCP Dokploy Online
by igoruam

customRole-update

Idempotent

Update a custom role's name and permissions in Dokploy to adjust access control for users or teams.

Instructions

POST /customRole.update

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>",
      "permissions": "<permissions>"
    },
    "name": "customRole-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNameYes
newRoleNameNo
permissionsYes

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?

The annotations supply only openWorldHint and idempotentHint, so the description carries the burden of disclosing mutation behavior and adds nothing. It never states that permissions may be overwritten, how the nested permission map replaces existing grants, or what authorization is required. The 'update' verb and openWorldHint are consistent with a write, so there is no contradiction, but no behavioral value is added.

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 economy of expression; a bare route string is not front-loaded useful information for an agent deciding whether to call the tool.

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 mutating tool with a nested permission object, two required parameters, and no output schema, the definition should explain rename versus permission replacement semantics. It provides none of that, so an agent cannot call it correctly without guessing.

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 parameters, one of which is a nested object mapping to arrays of permission strings. The description supplies no meaning for roleName versus newRoleName, nor the key/value shape of the permissions map, leaving the most consequential parameter semantics entirely undocumented.

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 route 'POST /customRole.update', which restates the tool name and HTTP method rather than stating in words what is updated on a custom role. An agent learns nothing about the resource beyond the name's own 'customRole-update' token.

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 mention of when not to use it, and no routing to alternatives such as customRole-create or customRole-remove for other lifecycle operations. Nothing in the text distinguishes this tool from its siblings.

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