Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-remove

Destructive

Removes a vault provider from Dokploy by vaultProviderId, letting you delete obsolete or unneeded credential providers from your deployment configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
vaultProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

The annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is established elsewhere. The description adds nothing beyond that – no statement about irreversible deletion of credentials, dependent applications, or error behavior – and does not contradict the annotations.

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 short because it is empty rather than efficient. A raw route string is not front-loaded information an agent can act on.

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, open-world mutation with an undocumented required parameter and no output schema, the definition provides essentially no context. An agent cannot determine safe invocation conditions from this text alone.

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 required parameter vaultProviderId has 0% schema description coverage, and the description supplies no meaning for it (no format, no source for obtaining an ID, no example). This is the one place the description needed to compensate and it does not.

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 /vaultProvider.remove" only restates the tool name as an HTTP route. It conveys deletion of a vault provider, but nothing about what a vault provider is, what removal entails, or how it differs from siblings such as vaultProvider-update or dnsProvider-remove.

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, no warning about consequences, and no pointer to alternatives. The agent must infer everything from the name alone.

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