Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-create

Creates a vault provider and assigns it to specified projects or environments, enabling centralized secret storage for Dokploy deployments.

Instructions

POST /vaultProvider.create

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

Input Schema

NameRequiredDescriptionDefault
nameYes
configYes
assignmentsYes

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 only supply a title and openWorldHint=true; they say nothing about mutation semantics, permissions, or reversibility, so the description carries the full burden and supplies none of it. Beyond the bare HTTP verb 'POST', it discloses no side effects, auth requirements, or what happens on duplicate names.

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 this is under-specification rather than conciseness: a single route string with no front-loaded statement of purpose or constraints. Nothing here earns its place as documentation.

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 three-required-parameter mutation tool with no output schema, zero schema coverage, and a free-form config object, the definition provides nothing an agent needs to call it correctly. It is a routing stub, not a tool description.

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 three required parameters (name, config, assignments), and the description adds no meaning whatsoever. Critically, 'config' is an unconstrained object whose expected keys an agent cannot guess from either the schema or the description.

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 route 'POST /vaultProvider.create', which restates the tool name and HTTP method rather than describing what a vault provider is or what creating one entails. It does imply a create operation on a vaultProvider resource, distinguishing it weakly from vaultProvider-update/remove, but nothing about the resource or outcome is explained.

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 tool, no prerequisites, and no mention of related siblings such as vaultProvider-update, vaultProvider-testConnection, or vaultProvider-one. An 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