Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-getServerMetrics

Read-onlyIdempotent

Retrieve server metrics from a Dokploy instance to monitor resource usage, infrastructure health, and diagnose capacity issues.

Instructions

GET /server.getServerMetrics

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "token": "<token>",
      "dataPoints": "<dataPoints>"
    },
    "name": "server-getServerMetrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
tokenYes
dataPointsYes

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 the safety profile is covered elsewhere. The description adds nothing beyond that: no mention of what metrics are returned, the time window, rate limits, or authentication expectations for the token parameter.

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?

The string is short but that is under-specification, not conciseness; it is neither front-loaded with useful information nor structured for a reader. Every sentence that would earn its place is absent.

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?

For a tool with three required undocumented parameters, no output schema, and an open-world remote endpoint, the description provides nothing an agent needs to call it correctly. It does not explain the endpoint's contract, required auth, or response shape.

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?

All three required parameters (url, token, dataPoints) have 0% schema description coverage, and the description supplies no meaning for any of them. It is unclear whether dataPoints is a count, a range, a selector, or a serialized structure, and the token's auth role is unstated.

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 route string "GET /server.getServerMetrics", which restates the tool name rather than describing it in prose. An agent can infer that it retrieves server metrics, but nothing distinguishes it from siblings like user-getServerMetrics or user-getContainerMetrics, and there is no verb/resource phrasing beyond the HTTP method.

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 guidance whatsoever on when to use this tool versus the many sibling metrics and server tools. The agent must infer scope (per-server vs user vs container) entirely from the tool 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