Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-getWebServerSettings

Read-onlyIdempotent

Retrieves the current Dokploy web server configuration so you can inspect server settings before adjusting infrastructure or troubleshooting deployment issues.

Instructions

GET /settings.getWebServerSettings

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

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?

The annotations already establish a read-only, idempotent, open-world operation, and the description's "GET" adds no meaningful behavioral context beyond them. It says nothing about whether values are live or cached, their scope, or any access requirements, though it does not contradict 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.

Conciseness3/5

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

The single method-and-endpoint string is short and contains no filler, but its brevity reflects under-specification rather than efficient explanatory writing. There is no front-loaded plain-language statement of purpose or scope.

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?

Although a zero-argument read is simple to invoke, the absence of an output schema makes the lack of explanatory scope more consequential. The definition does not identify the returned settings or provide enough context to select this general tool confidently over related web-server and Traefik tools.

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 has zero parameters, so there is no parameter meaning that the description needs to clarify; the baseline score for a parameterless tool applies. The schema also explicitly disallows additional properties, making invocation straightforward.

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's "GET" and endpoint imply retrieval of web server settings, but otherwise it merely restates the tool identifier. It does not explain what those settings contain or distinguish this tool from siblings such as settings-readWebServerTraefikConfig or settings-getTraefikPorts.

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 explicit guidance about when to retrieve these settings, what questions the tool answers, or when a more specific settings tool would be preferable. Usage can only be inferred from the name and sibling names.

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