Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-create

Creates a Dokploy storage destination by registering the provider, bucket, region, endpoint, and access credentials needed for deployments.

Instructions

POST /destination.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>",
      "provider": "<provider>",
      "accessKey": "<accessKey>",
      "bucket": "<bucket>",
      "region": "<region>",
      "endpoint": "<endpoint>",
      "secretAccessKey": "<secretAccessKey>"
    },
    "name": "destination-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
bucketYes
regionYes
endpointYes
providerYes
serverIdNo
accessKeyYes
additionalFlagsNo
secretAccessKeyYes

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?

The only annotation is openWorldHint=true and a title, so readOnly/destructive semantics are undeclared and the description carries the full burden. It discloses nothing about mutation effects, required credentials/permissions, idempotency, or what happens if a destination with the same name exists — especially notable since the schema requires accessKey and secretAccessKey, implying a credential-handling operation.

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 HTTP route string that omits all operationally necessary content. There is no structure, no front-loaded purpose statement, and the single token of information does not earn its place as a description.

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 mutation tool with 9 parameters, 7 required including secret material, a boolean openWorld annotation, and no output schema, the description is completely inadequate. An agent cannot safely call this tool from the definition alone and would have to guess at S3-compatible semantics and credential requirements.

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?

The tool has 9 parameters (7 required) with 0% schema description coverage, and the description supplies no meaning for any of them. Critical ambiguities — what 'provider' values are valid, what 'serverId' refers to, what format 'additionalFlags' takes, or how endpoint/region relate — are left entirely unresolved.

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 /destination.create" only restates the tool name as an HTTP route; it names the resource (destination) and implies creation, but adds no distinguishing scope versus siblings like destination-update or destination-testConnection. This is essentially a tautology of the tool name rather than a statement of what the tool does or returns.

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 guidance on when to use this versus destination-update, destination-testConnection, or destination-all. An agent must infer that 'create' means provisioning a new storage destination, with no prerequisites, ordering, or exclusion information provided.

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