Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-setup

Idempotent

Configures a Dokploy server using its server ID to prepare it for deployment and infrastructure management.

Instructions

POST /server.setup

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": {
      "serverId": "<serverId>"
    },
    "name": "server-setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 repeat safety and external-world interaction are already covered structurally. The description adds no behavioral detail beyond that: no side effects, permissions, blocking duration, or state changes are described, and a one-line endpoint restatement contributes nothing over the annotations.

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 is under-specification rather than efficiency. The sole content is a route token, with no front-loaded explanation of purpose or constraints.

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 an idempotent, open-world setup operation requiring an identifier and lacking an output schema, the agent needs to know what setup does and what the identifier identifies. None of that is supplied, so the definition is not complete enough to invoke the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0% and the single required serverId has no description in the schema. The description also says nothing about what serverId refers to (an existing server, a target to be created, or its format), so the lone parameter is undocumented everywhere.

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 /server.setup", which restates the tool name rather than stating what setup actually does (provision, install, configure, or register a server). It gives no verb-plus-outcome that would distinguish it from siblings like server-create or settings-updateServer.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives are provided. With several plausible sibling alternatives such as server-create, server-validate, or settings-updateServer, the definition offers zero routing signal and leaves the agent to infer usage from the 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