Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-getLogCleanupStatus

Read-onlyIdempotent

Retrieves Dokploy's log cleanup status to show whether automatic log cleanup is enabled and what cleanup settings are configured.

Instructions

GET /settings.getLogCleanupStatus

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-getLogCleanupStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing on top — no statement of what the status reflects, whether cleanup is running, what triggers it, or how it relates to the cleanup operations. The "GET" prefix is consistent with the annotations but conveys nothing beyond them.

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 a single URL path fragment with no prose structure, no front-loaded intent, and no supporting sentence. Brevity here is under-specification rather than concision — it is short because it says almost nothing.

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?

There is no output schema, so the description would need to explain what the returned cleanup status contains (last run, schedule, in-progress flag) and it does not. For a zero-parameter read tool the bar is low, but a bare route string leaves the agent unable to predict the response shape or when the call is worthwhile.

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 zero parameters and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies; no parameter-level gap exists.

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 entire description is the raw route string "GET /settings.getLogCleanupStatus", which simply restates the tool name. There is no verb describing the action (retrieve/read) and no object beyond the name itself, so it adds no meaning an agent could not infer from the identifier. It is a restatement rather than a purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to call this versus settings-updateLogCleanup, settings-cleanAll, or settings-cleanAllDeploymentQueue, all of which appear in the sibling list. An agent must guess whether this is a read-only inspection before a cleanup or something else. No prerequisites, no mention of what condition warrants checking the status.

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