Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-all

Read-onlyIdempotent

Lists all vault providers configured in a Dokploy instance to help identify available credential sources for secret management.

Instructions

GET /vaultProvider.all

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vaultProvider-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own: nothing about what 'all' means, whether results are paginated or filtered by permissions, or what a vault provider record contains.

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?

The text is short but it is an under-specified endpoint path rather than a concise description; brevity here costs information instead of saving it. One additional sentence naming the resource and return shape would have been far better value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place return values could be explained, and it says nothing about the response shape, size, or ordering of the 'all' listing. For a simple zero-parameter read this is a notable omission rather than a fatal one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema (with additionalProperties=false) fully documents the input contract and there is no parameter meaning left for the description to add. Baseline 4 applies for a no-parameter tool.

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 raw endpoint 'GET /vaultProvider.all', which essentially restates the tool name 'vaultProvider-all' rather than describing the operation in prose. An agent can infer it retrieves vault providers, but nothing distinguishes it from 'vaultProvider-one' or 'vaultProvider-listSecretNames' beyond the path string.

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 exclusion of alternatives, and no stated preconditions. The agent must guess whether this is the right call versus 'vaultProvider-listSecretNames' or 'vaultProvider-one'.

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