Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-remove

Destructive

Remove a DNS provider from Dokploy by its ID to clean up unused or misconfigured DNS integrations.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
dnsProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/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 needs to add consequences, irreversibility, or side effects. It adds nothing at all beyond the HTTP verb and path, leaving the agent with no idea what the removal destroys or whether it cascades to records/zones.

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 shortness here reflects under-specification rather than efficiency. There is no front-loaded statement of effect or any structure beyond a bare route string.

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?

This is a destructive, one-parameter mutation with no annotations beyond the destructive flag, no output schema, and no parameter documentation. The description does none of the work required for an agent to call it safely and correctly.

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 description coverage is 0% for the single required parameter dnsProviderId; the description provides no clarification of identifier format, source, or constraints. Only the parameter's self-evident name carries meaning.

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 /dnsProvider.remove" merely restates the tool name and its transport route. The only semantic content is the word "remove," from which an agent can infer deletion of a DNS provider, but no resource scope or effect is stated.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as dnsProvider-update or the record-level tools. The agent must infer everything from the sibling 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