Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-allForPermissions

Read-onlyIdempotent

Lists every permission configured for a Dokploy server, helping you review user and role access before changing deployment or infrastructure settings.

Instructions

GET /server.allForPermissions

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": "server-allForPermissions"
  }
}

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=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the verb — no indication of return shape, result volume, pagination, or what "allForPermissions" entails, which matters because openWorldHint suggests a potentially large external call.

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 is under-specification rather than conciseness — a raw route string is not a front-loaded explanation. Nothing in it helps an agent decide or prepare a call.

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?

With no parameters and no output schema, the description carries the entire burden of explaining what the call yields, and it fails to do so. For a list-style endpoint in a crowded namespace of near-identical *-allForPermissions siblings, an agent has no basis to choose correctly.

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 closed (additionalProperties=false, 100% coverage), so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

"GET /server.allForPermissions" only restates the tool name with its HTTP verb. It does not say what is being listed — servers, permissions, or servers filtered by permission — so an agent cannot tell what resource it returns or how it differs from siblings such as project-allForPermissions or user-getPermissions.

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 exclusions, and no mention of the clearly related siblings (project-allForPermissions, gitProvider-allForPermissions, user-getPermissions). The agent must guess whether this is the right call for a permissions-related question.

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