Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-isCloud

Read-onlyIdempotent

Retrieves the isCloud setting from a Dokploy instance to determine whether the deployment platform runs in cloud mode or self-hosted, helping clients adapt behavior and configuration.

Instructions

GET /settings.isCloud

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-isCloud"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 them: it does not say whether the call hits a remote cloud service, whether it can fail when unauthenticated or offline, or what shape the answer takes. For an open-world read with no output schema, that is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded phrase with zero padding, which is structurally clean. However, the brevity is under-specification rather than efficiency — the one sentence present is a route string, not an explanation.

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 full burden of explaining what isCloud returns (a boolean? a nested cloud config?) and under what conditions it applies. None of that is present, so an agent cannot confidently interpret the result.

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, so there is nothing for the description to disambiguate; baseline is 4. No parameter-related omission hurts callability.

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 a raw route restatement, "GET /settings.isCloud", which largely echoes the tool name. It implies reading an 'isCloud' flag but never states what that flag means (e.g., whether the instance runs on Dokploy Cloud) or why an agent would want it, so it does little more than the name already does.

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 exclusion, and no routing to alternatives such as settings-isUserSubscribed or settings-getDokployCloudIps, which plausibly overlap. The agent must infer entirely 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