Skip to main content
Glama
MCP Dokploy Online
by igoruam

mounts-remove

Destructive

Removes a specified mount from a Dokploy instance by mount ID, helping clean up unused storage or volume configurations.

Instructions

POST /mounts.remove

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": {
      "mountId": "<mountId>"
    },
    "name": "mounts-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
mountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description need not restate safety. However, it adds nothing beyond them: no explanation of consequences (e.g., whether attached services break), no auth or confirmation requirements, no idempotency note. Since annotations carry the safety profile, the bar is lower, but the description still fails to add any behavioral context.

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?

Extremely short but not front-loaded with meaning; it is under-specified rather than concise. The one phrase present is an HTTP path that adds no value beyond the tool name.

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?

For a destructive mutation with no output schema and 0% parameter coverage, the description should explain consequences and identifier semantics. It provides none of this, leaving the agent to infer everything from annotations and the name.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter mountId is undocumented in both schema and description. The path 'mounts.remove' implies a mount identifier is required, but the description never explains format, where to obtain the ID, or whether removal is by ID 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 is only 'POST /mounts.remove', a restatement of the tool name (mounts-remove) with an HTTP verb. It does not state what a mount is, what removing one does, or how it differs from siblings like mounts-update or mounts-listByServiceId.

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?

No guidance on when to use this versus alternatives such as mounts-update (to modify) or other remove tools. Nothing indicates prerequisites or when removal is appropriate.

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