Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-remove

Destructive

Remove a container registry from Dokploy by registry ID to delete its stored credentials and configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
registryIdYes

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 danger profile is known. The description adds nothing beyond that — no statement of whether deletion is permanent, whether dependent resources are cascaded, or whether confirmation is 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?

It is short, but brevity here is under-specification rather than efficiency: a bare route string with no verb-object statement or scope is not useful front-loaded content.

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 destructive mutation with an undocumented required identifier and no output schema, the definition supplies nothing an agent needs to call it safely — no target semantics, no effects, no return behavior.

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% and the single required registryId parameter is undocumented. The description provides no meaning, format, or example for it, so the parameter is entirely opaque to the agent.

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 /registry.remove", which restates the name and implies deletion but never states what resource is being removed or what a 'registry' is in this system. An agent gets only the verb 'remove' inferred from the path, not a described action.

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?

There is no indication of when to use this rather than registry-update, registry-one, or the other remove siblings, nor any prerequisite (e.g. registry must exist, must be empty). Nothing distinguishes it from the large family of *-remove tools.

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