Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getServerHealth

Read-onlyIdempotent

Retrieve Docker server health status and metrics for a specified server and time window to diagnose availability and performance issues.

Instructions

GET /docker.getServerHealth

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": "docker-getServerHealth"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
sinceHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 safety is covered. The description adds nothing beyond that: no scope of the health check, no auth requirements, no note on latency or what a failing server looks like. A route string alone earns little credit.

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 technically short, but the brevity is under-specification rather than concision — a single URI fragment that front-loads nothing useful. There is no wasted sentence because there is essentially no sentence.

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 no output schema and 0% parameter coverage, the description needed to explain what a health response contains and how the time window affects it. It supplies none of that, so an agent cannot predict results or call the tool with justified arguments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for both parameters and does not. It never explains that serverId selects a target server or that sinceHours bounds the observation window (capped at 168 hours), leaving an agent to guess the windowing semantics from the parameter name alone.

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 only restates the tool name as an HTTP route ("GET /docker.getServerHealth"). It conveys that a read happens but never says what "health" means here — container states, daemon reachability, resource pressure — nor how it differs from siblings such as settings-health or settings-checkInfrastructureHealth.

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 mention of alternatives, despite several sibling tools (settings-health, settings-checkInfrastructureHealth, server-getServerMetrics) covering overlapping health/metrics territory. An agent has nothing to route on beyond 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