Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-getPermissions

Read-onlyIdempotent

Retrieve the authenticated user's permissions to verify which Dokploy actions and resources they can access.

Instructions

GET /user.getPermissions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description gets a lower bar, but it contributes nothing beyond them. It does not disclose whose permissions are returned, whether the caller must be an admin, or anything about response size or scope.

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?

Nothing is wasted because almost nothing is said; the single route token is not front-loaded information but a label. This is under-specification rather than effective brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with no params and no output schema, the description still omits the essentials: whether it returns the caller's own permissions or another user's, and what the payload contains. Annotations cover the safety profile but not the semantics of the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is fully described, so there is no parameter meaning the description needed to add. Baseline 4 applies for a parameterless tool.

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 just the HTTP route string "GET /user.getPermissions", which restates the tool name rather than explaining the operation. It implies permission retrieval, but not whose permissions, for what scope, or in what shape, so it cannot be distinguished from siblings like user-haveRootAccess or user-assignPermissions.

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 at all — no conditions, no prerequisites, and no mention of alternatives such as user-haveRootAccess or the permission-listing siblings. An agent must infer the use case entirely from the route name.

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