Skip to main content
Glama
MCP Dokploy Online
by igoruam

vaultProvider-one

Read-onlyIdempotent

Retrieves a specific vault provider by ID from a Dokploy instance so you can inspect its configuration and details.

Instructions

GET /vaultProvider.one

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": "vaultProvider-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 safety and idempotency are covered by structured data. The description adds nothing on top of that — no note on behavior for a nonexistent ID, no auth/tenant scoping, no indication of what the 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?

Five words of HTTP verb-plus-path are technically terse but represent under-specification rather than conciseness. There is no wasted wording, but there is also almost no content for the agent to act on.

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?

The tool is simple (one parameter, no output schema, annotations covering safety), so a short description could suffice — but this one still leaves the parameter's meaning and the not-found behavior entirely unaddressed. It is a route stub rather than a definition an agent can confidently invoke.

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

Parameters2/5

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

The single required parameter has 0% schema description coverage, so the schema supplies only its type and minLength. The description does nothing to compensate: it never mentions vaultProviderId, its expected format (slug, UUID, numeric?), or where an agent would find one.

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?

"GET /vaultProvider.one" merely restates the tool name and title as an HTTP route. It conveys no resource semantics beyond the identifier (a vault provider) and gives no hint of what a single fetch returns or what distinguishes it from 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 prerequisite information, and no mention of the obvious alternative (vaultProvider-all) or of how to obtain a valid ID. An agent must infer from the name alone that this retrieves one provider by ID.

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