Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-update

Idempotent

Update a vault provider's name, configuration, and project or environment assignments in Dokploy to keep secrets access aligned with your infrastructure.

Instructions

POST /vaultProvider.update

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": "<name>",
      "config": "<config>",
      "assignments": "<assignments>"
    },
    "name": "vaultProvider-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
configYes
assignmentsYes
vaultProviderIdYes

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 supply openWorldHint=true and idempotentHint=true, and the description adds nothing beyond them. It does not disclose what gets overwritten (full-replace vs partial), whether credentials are re-validated, permission requirements, or side effects on assignments — critical context for a mutation tool.

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 conciseness. A single route fragment with no front-loaded purpose sentence, no parameter notes, and no usage framing does not earn its place as a definition.

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 four-required-parameter mutation tool with no output schema and a nested assignments array, the definition is completely inadequate. Nothing tells the agent the required shape of a valid call, what a successful update returns, or what happens to omitted configuration.

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% across four required parameters, so the description must compensate and does not. It gives no meaning for vaultProviderId, name, the opaque config object, or the assignments array with its environmentIds default, leaving an agent to guess semantics entirely from the raw schema.

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 the HTTP route 'POST /vaultProvider.update', which restates the tool name rather than stating what the tool does. It implies an update to a vault provider but does not say what is being changed (name, config, assignments) or how it differs from vaultProvider-create or vaultProvider-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 at all. With siblings like vaultProvider-create and vaultProvider-remove present, the definition gives no signal about selection, prerequisites, or conditions under which an update is appropriate versus creating a new provider.

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