Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-remove

Destructive

Removes a MongoDB service from Dokploy by its mongoId, enabling cleanup of unused database resources.

Instructions

POST /mongo.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": {
      "mongoId": "<mongoId>"
    },
    "name": "mongo-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

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 already flag destructiveHint=true and openWorldHint=true, but the description adds nothing: it does not say what data is destroyed, whether the deletion is reversible, whether running instances must be stopped first, or whether backups survive. For a destructive operation this is a critical gap.

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 one short line, but brevity here comes from under-specification rather than discipline; there is no front-loaded statement of what the tool does or what the caller must supply.

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?

A destructive, irreversible-looking tool with one undocumented required identifier, no annotations covering scope of destruction, and no output schema. The definition supplies none of the context an agent needs before invoking it.

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 parameter mongoId has 0% schema description coverage and the description says nothing about it — no format, no source, no indication of whether it is the Mongo service ID or something else. The description does not compensate for the schema gap at all.

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?

"POST /mongo.remove" only restates the tool name and routing verb; it never says what resource is deleted or what a Mongo instance is in this product. An agent learns nothing about the operation beyond the fact that it is an HTTP POST to a removal endpoint.

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 versus mongo-stop, cluster-removeWorker, deployment-removeDeployment, or the other removal siblings. No preconditions are stated, and the destructive nature makes the absence of guidance especially costly.

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