Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-getContainerMetrics

Read-onlyIdempotent

Retrieves container metrics for a specified Dokploy application using your instance URL, token, app name, and desired data points for monitoring and diagnostics.

Instructions

GET /user.getContainerMetrics

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>",
      "appName": "<appName>",
      "dataPoints": "<dataPoints>"
    },
    "name": "user-getContainerMetrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
tokenYes
appNameYes
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, idempotentHint, and openWorldHint, so the safety profile is covered by structured data. The description adds nothing beyond that — no note on authentication, rate limits, metric resolution, or time-window behavior for a network-fetching operation.

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 brief, but brevity here comes from under-specification rather than from efficient phrasing. The single endpoint-path fragment carries no front-loaded purpose statement an agent can act on.

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?

A tool requiring a URL, auth token, app name, and a data-points argument, with no output schema and no annotations explaining payload shape, needs a real description. Nothing about request construction or returned metrics is conveyed.

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 four required parameters (url, token, appName, dataPoints) have zero schema description coverage, and the description supplies no meaning for any of them — notably the ambiguous 'dataPoints' string and how 'appName' scopes the query.

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 endpoint path "GET /user.getContainerMetrics", which essentially restates the tool name. It does not explain what container metrics are returned, what a data point means, or how it differs from siblings such as user-getServerMetrics or swarm-getContainerStats.

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, when-not-to-use, or alternative guidance at all. An agent cannot tell from this string why it would choose container metrics over server metrics or the swarm container stats tool.

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