Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-listSecretNames

Read-onlyIdempotent

Lists secret names from a specified vault provider within a Dokploy project, optionally scoped to an environment, so you can identify available secrets without retrieving their values.

Instructions

GET /vaultProvider.listSecretNames

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>",
      "projectId": "<projectId>"
    },
    "name": "vaultProvider-listSecretNames"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
environmentIdNo
vaultProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 structurally. The description adds nothing beyond that — no note on whether secret values are ever exposed (a real concern when listing secrets), no pagination or rate-limit context, and no indication that this hits an external vault over the network despite openWorldHint.

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 only because it is under-specified rather than economical; the single line conveys no information beyond the endpoint path. There is no structure, front-loading, or explanatory content to evaluate.

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 tool that reads from an external secrets store with two required scoping parameters and no output schema, the definition gives an agent nothing to work with. Whether the response is an array of names, a map, or paged results is unknown, and the required/nullable distinction for environmentId is unaddressed.

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 parameters (vaultProviderId, projectId, environmentId), so the description carries the full burden and provides nothing. The distinction between projectId and environmentId scoping, and whether environmentId is optional narrowing of results, is completely undocumented.

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 string "GET /vaultProvider.listSecretNames", which restates the tool name rather than explaining what it does. An agent can infer it lists secret names for a vault provider, but nothing is stated about scope, return contents, or how it differs from sibling listing tools like dnsProvider-listRecords or vaultProvider-all.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 mention of alternatives. The agent is left to infer usage entirely from the tool name and the presence of vaultProvider-one/vaultProvider-all siblings.

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