Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-testConnection

Idempotent

Tests connectivity to a configured vault provider using its connection settings, verifying that the provider can be reached before you rely on it for secrets management.

Instructions

POST /vaultProvider.testConnection

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-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNo
vaultProviderIdNo

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?

Annotations already declare openWorldHint=true and idempotentHint=true, so the safe/idempotent network-call profile is known. The description adds nothing beyond that: it does not say whether credentials are validated, whether anything is persisted, what a failure response looks like, or whether config is required versus an existing vaultProviderId.

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 bare endpoint path carries no information an agent could act on. A brief sentence on the tested resource and expected outcome would cost little and add much.

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?

No output schema, no annotations explaining results, and zero parameter documentation, yet the tool takes an ambiguous config object and returns connection status the agent cannot anticipate. Nothing tells the agent how to interpret success or failure, which is the entire point of a test-connection tool.

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% for both parameters. The description provides no meaning for `config` (an unconstrained free-form object) or `vaultProviderId`, nor explains their relationship or which to supply when. With zero coverage, the description had full responsibility and supplied none.

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.testConnection" merely restates the tool name and its HTTP method. The agent can infer a connectivity test for a vault provider, but there is no verb+resource description of what is actually validated or what the result means.

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?

No when-to-use guidance, no prerequisites, and no mention of how this differs from sibling testConnection tools or from vaultProvider-create/update. The agent must guess when to call it.

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