Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-setupGPU

Idempotent

Sets up GPU support for a specified Dokploy server, enabling GPU-backed workloads and deployments.

Instructions

POST /settings.setupGPU

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": "settings-setupGPU"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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?

Annotations only supply openWorldHint=true and idempotentHint=true; the description adds nothing about what GPU setup actually changes, whether it is destructive, what permissions or host access it needs, or whether it is safe to re-run. For a mutation-style POST with a weak annotation profile, the description carries most of the burden and delivers none of it.

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 — a bare endpoint path with no front-loaded explanation of purpose or effect. Nothing in the one line earns its place as documentation.

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?

With no output schema, no parameter documentation, and only two weak annotations, the description is the sole remaining channel for meaning and provides none. An agent has no way to determine effects, side effects, or prerequisites before invoking it.

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?

The single parameter serverId has 0% schema description coverage and the description never mentions it. The agent must guess whether serverId is the target host, an optional filter, or required context for the GPU operation.

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 HTTP route string "POST /settings.setupGPU", which restates the tool name in REST form rather than stating what the tool does. An agent cannot tell whether this installs GPU drivers, enables GPU passthrough, or registers a GPU-enabled server, and there is no differentiation from siblings like settings-checkGPUStatus.

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 reference to any alternative tool. The presence of settings-checkGPUStatus among siblings makes the omission of a use/exclusion rule especially costly, and nothing in the definition fills that gap.

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