Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-updateBuildsConcurrency

Idempotent

Configure the maximum concurrent builds allowed on a server to manage build capacity and avoid resource contention.

Instructions

POST /server.updateBuildsConcurrency

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>",
      "buildsConcurrency": "<buildsConcurrency>"
    },
    "name": "server-updateBuildsConcurrency"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes
buildsConcurrencyYes

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 openWorldHint=true and idempotentHint=true, but the description adds nothing about permissions, whether the change affects running builds, or what happens at the 1-100 boundaries. For a mutation endpoint with no destructiveHint declared, this leaves the behavioral burden entirely unmet.

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 this is under-specification rather than conciseness — a single URL fragment that carries no explanatory content. There is no front-loaded statement of purpose to structure around.

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 two required parameters at zero schema description coverage, no output schema, and mutation semantics, the definition should explain the parameters and effect of the change. It explains nothing, so an agent could not confidently invoke 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?

Schema description coverage is 0% for both required parameters, and the description does not compensate: 'buildsConcurrency' is never explained as a concurrency ceiling or given units/effects, and 'serverId' is never identified as the target server identifier. The bare endpoint path conveys no parameter meaning at all.

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 endpoint string "POST /server.updateBuildsConcurrency", which merely restates the tool name and method. It never states in plain language what the operation does (e.g., setting a per-server cap on simultaneous builds), so an agent gains no understanding beyond the name.

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 the closely named sibling settings-updateBuildsConcurrency, which the agent must distinguish this from. Nothing indicates when this server-scoped variant is the right choice.

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