Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-checkInfrastructureHealth

Read-onlyIdempotent

Checks the health of your Dokploy infrastructure to verify services and settings are operational, helping you diagnose deployment or connectivity issues.

Instructions

GET /settings.checkInfrastructureHealth

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: no indication of what is probed, whether calls are expensive, or how failures surface.

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 not verbose, but it is under-specified rather than concise — a single route string that carries no explanatory content. Nothing is front-loaded because nothing is said.

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?

For a no-parameter diagnostic tool with no output schema, the description should at least say what is inspected and roughly what the result indicates. Instead it gives only the route, leaving the agent unable to predict the response or distinguish this from neighboring health checks.

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 and the input schema is empty with additionalProperties=false, so there is no parameter meaning for the description to supply. With no arguments to document, the description is not leaving a semantic gap here.

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 just the HTTP route 'GET /settings.checkInfrastructureHealth', which restates the tool name rather than explaining what is checked or what 'infrastructure health' covers. An agent gets no more information from the description than from the name alone, and nothing distinguishes it from settings-health or docker-getServerHealth.

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 prerequisites, and no mention of when an agent should prefer this over the many sibling health/settings tools. The endpoint name is the only hint that this is a diagnostics call.

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