Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-setupMonitoring

Idempotent

Configures server and container monitoring by setting refresh rates, retention, thresholds, and callback details so Dokploy can track infrastructure health and alert on CPU or memory issues.

Instructions

POST /server.setupMonitoring

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": {
      "serverId": "<serverId>",
      "metricsConfig": "<metricsConfig>"
    },
    "name": "server-setupMonitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes
metricsConfigYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond that – no statement of what monitoring configuration gets created or overwritten, what permissions are required, or whether an existing configuration is replaced. The description carries no behavioral information at all.

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 text is brief, but its brevity comes from omission rather than efficiency – a single route string that conveys nothing actionable. There is no structure, no front-loaded purpose, and no content that earns its place.

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 deeply nested required configuration (server metrics plus container include/exclude lists), no output schema, and no annotations covering input semantics, the description is wholly inadequate. An agent could not construct a valid call from this definition alone.

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?

Schema description coverage is 0% across two required parameters whose nested objects contain many required sub-fields (token, urlCallback, cronJob, thresholds, services). The description explains none of them, leaving the agent with bare property names and validation constraints only.

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, 'POST /server.setupMonitoring'. It hints that monitoring gets configured for a server but names no verb-level outcome, no scope, and nothing that separates it from siblings like admin-setupMonitoring or settings-cleanMonitoring.

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. An agent cannot tell from this text why it would pick this tool over admin-setupMonitoring or server-getServerMetrics.

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