Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanUnusedImages

Idempotent

Removes unused Docker images from a specified Dokploy server to reclaim disk space and keep deployments clean.

Instructions

POST /settings.cleanUnusedImages

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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 only declare openWorldHint and idempotentHint; the destructive nature of deleting images on a server (and whether it is reversible) is never disclosed. The description adds nothing beyond the endpoint string, leaving the agent unaware this is an irreversible cleanup.

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 short, but that is under-specification rather than conciseness: one bare route line with no front-loaded purpose, scope, or caution.

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?

With no output schema, no parameter documentation, and only two hints in annotations, the description leaves the agent without the information needed to invoke a destructive cleanup safely.

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?

The single serverId parameter has 0% schema description coverage, and the description offers no meaning for it. The agent cannot tell whether omitting serverId scopes the cleanup locally, to all servers, or fails.

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 just the HTTP route 'POST /settings.cleanUnusedImages', which essentially restates the tool name. It implies a cleanup of unused images but never states what 'unused' means or how it differs from siblings like settings-cleanUnusedVolumes or settings-cleanDockerPrune.

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 guidance on when to use this tool versus the many other clean* siblings, no prerequisites, and no warning about when it should not be run. An agent must guess entirely from the tool name.

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