Skip to main content
Glama
MCP Dokploy Online
by igoruam

swarm-getContainerStats

Read-onlyIdempotent

Retrieves container resource statistics from a Dokploy swarm server by server ID, helping you monitor CPU, memory, and performance for deployed services.

Instructions

GET /swarm.getContainerStats

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": "swarm-getContainerStats"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 and idempotency are covered structurally. The description adds nothing beyond the implicit 'GET', disclosing no return shape, no freshness/live-vs-cached semantics, no auth or rate-limit context, and no behavior for missing or unreachable servers.

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 only because it is under-specified rather than dense. The text is a bare endpoint path with no front-loaded purpose statement, so brevity buys the reader nothing.

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?

No output schema exists and the schema coverage is 0%, so the description carried the full burden of explaining the call and returned nothing. For a stats-retrieval tool whose result format is entirely undefined, this leaves an agent unable to invoke it with confidence.

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 optional parameter serverId has 0% schema description coverage, and the description never mentions it at all. With only one parameter and no compensating text, an agent cannot tell what serverId identifies, whether omitting it means 'all servers' or a local default, or what format it takes.

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 raw route 'GET /swarm.getContainerStats', which restates the tool name in HTTP terms rather than stating what the tool does. It implies retrieval of container statistics for the Swarm, but gives no scope, aggregation, or identification details, and does nothing to separate it from siblings like swarm-getNodeInfo or user-getContainerMetrics.

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 or when not to use it. An agent has to guess whether it needs a serverId, a swarm context, or a running container.

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