Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateBuildsConcurrency

Idempotent

Set the concurrent build limit in Dokploy settings (1–100) to control build resource usage and prevent overload.

Instructions

POST /settings.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": {
      "buildsConcurrency": "<buildsConcurrency>"
    },
    "name": "settings-updateBuildsConcurrency"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 only declare openWorldHint=true and idempotentHint=true; the description adds nothing about permissions, scope of effect, ranges, or whether the change applies globally versus per-server. With no write/read hints and no explanatory text, an agent cannot tell whether this is a global mutation or what it affects. It does not contradict the annotations, but it carries zero additional behavioral information.

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 by omission, not by efficiency: the entire text is a route string and no actual content is front-loaded. There is nothing to trim, yet nothing informative is delivered.

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?

A mutation tool with one required, bounds-constrained parameter and no output schema needs the description to explain effect, scope, and the meaning of the value. None of that is present, leaving the definition inadequate for correct invocation.

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 buildsConcurrency has 0% schema description coverage and the description says nothing about it. The schema only supplies type integer with minimum 1 and maximum 100; the description does not explain what the number controls, units, or consequences of the value, so the parameter is effectively undocumented.

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 "POST /settings.updateBuildsConcurrency", which restates the tool name rather than explaining what the tool does. It conveys no specifics about builds concurrency semantics (e.g., whether it caps a queue or sets a per-server limit) and does nothing to distinguish it from the sibling server-updateBuildsConcurrency.

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 guidance on when to use this tool, when not to, or which sibling to pick for related concurrency settings. The agent must infer everything from the name alone.

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