Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateLogCleanup

Idempotent

Updates the cron schedule that controls automatic log cleanup on a Dokploy instance, so old logs are removed according to your desired timing.

Instructions

POST /settings.updateLogCleanup

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": {
      "cronExpression": "<cronExpression>"
    },
    "name": "settings-updateLogCleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
cronExpressionYes

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 openWorldHint=true and idempotentHint=true, so the safety/behavior profile is partly covered structurally. The description adds nothing beyond the route: it does not say what changes on the server, whether the previous schedule is replaced, or what happens to existing cleanup state. Since POST implies a mutation, some disclosure of effect would be expected.

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 short but that is under-specification rather than conciseness; a bare route string conveys no actionable information and there is no structure or front-loaded intent.

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 mutation endpoint with a required, undocumented cron parameter and no output schema, the description should carry the full explanatory burden. Instead it provides only the transport path, leaving everything an agent needs to call it correctly unspecified.

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% with one required parameter, cronExpression, and the description supplies no meaning at all for it — not its expected format, not whether null disables cleanup. With a required param fully undocumented in both schema and description, this is a clear gap.

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 HTTP route "POST /settings.updateLogCleanup", which restates the tool name in URL form rather than stating in words what the tool does or what gets configured. An agent can guess it modifies log-cleanup settings, but the description never says so explicitly and offers no differentiation from siblings like settings-getLogCleanupStatus.

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 reading current status first via settings-getLogCleanupStatus. The HTTP verb is the only hint about context.

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