Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanMonitoring

Idempotent

Cleans monitoring data and resets related settings on a Dokploy instance to remove stale metrics and free storage without affecting deployments.

Instructions

POST /settings.cleanMonitoring

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": "settings-cleanMonitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

Annotations declare openWorldHint=true and idempotentHint=true, and the description adds nothing beyond them. It does not disclose what gets removed, whether the action is destructive or reversible, or whether elevated permissions are needed — critical context for a 'clean' operation. No direct contradiction, but zero added value.

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 certainly short, but the brevity comes from under-specification rather than efficiency: a single endpoint path with no front-loaded explanation of the action or its effect. Nothing here helps an agent decide or act.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations covering destructiveness, the description carries the full burden of explaining what a monitoring-cleanup endpoint does and what state it leaves behind, and it does none of that. A zero-parameter tool is simple, but 'clean' is an ambiguous mutation that requires explanation.

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

Parameters4/5

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

The tool takes no parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to explain. Baseline for a zero-parameter tool applies.

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 string 'POST /settings.cleanMonitoring', which effectively restates the tool name as an HTTP endpoint. It never says in plain language what is being cleaned (monitoring data, containers, config) or what the effect is, so the agent must guess from the name alone.

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 such as admin-setupMonitoring, server-setupMonitoring, or application-readAppMonitoring that an agent would need to distinguish setup vs. read vs. clean operations. The route path provides no decisional information.

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