Skip to main content
Glama
MCP Dokploy Online
by igoruam

customRole-create

Create a custom Dokploy role by specifying a role name and permissions to control user access precisely.

Instructions

POST /customRole.create

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-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNameYes
permissionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only title and openWorldHint; there is no readOnly or destructive hint. The description adds nothing about mutation effects, required permissions or scope, whether the role is immediately active, or what is returned. For a write operation with essentially no annotation coverage, this is a serious gap.

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 that brevity comes from under-specification rather than economy. The single line is an endpoint path and carries no usable information for an 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?

Two required parameters, a nested object, no output schema, and near-zero annotation detail mean the description should carry most of the burden. It carries none, leaving an agent unable to construct a valid call.

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% and the description explains neither parameter. Most critically, the nested 'permissions' object (map of resources to string arrays) is entirely undocumented, so an agent cannot know the expected key/value structure from either source.

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 "POST /customRole.create", which restates the tool name as an HTTP route rather than stating what the tool does. It implies role creation but does not say what a custom role is, what it contains, or how it differs from customRole-update or customRole-remove.

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 prerequisites, and no mention of any alternative despite several sibling tools (customRole-update, customRole-remove, customRole-all) that an agent must choose between.

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