Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-update

Idempotent

Updates an existing Dokploy deployment target's provider, bucket, region, endpoint, and credentials to keep storage configuration current.

Instructions

POST /destination.update

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>",
      "accessKey": "<accessKey>",
      "bucket": "<bucket>",
      "region": "<region>",
      "endpoint": "<endpoint>",
      "secretAccessKey": "<secretAccessKey>",
      "destinationId": "<destinationId>",
      "provider": "<provider>"
    },
    "name": "destination-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
bucketYes
regionYes
endpointYes
providerYes
serverIdNo
accessKeyYes
destinationIdYes
additionalFlagsNo
secretAccessKeyYes

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 state openWorldHint=true and idempotentHint=true, so the description is not the primary carrier of behavior. The path confirms a mutating POST, but the description says nothing about required credentials, whether omitted fields are reset, or whether updates can be partially applied.

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 and front-loaded, but only because it carries almost no content. Conciseness here reflects under-specification rather than efficient communication.

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 10-parameter mutating tool with no output schema and 0% schema coverage, this description does nothing to prepare an agent to invoke it correctly. It lacks field semantics, credential requirements, and any indication of the response behavior.

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 10 parameters (8 required), and the description mentions none of them. Names like accessKey, secretAccessKey, bucket, region, endpoint, and provider are left entirely unexplained, including whether credentials must be re-supplied on every update.

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.update" essentially restates the tool name plus the HTTP method and path. An agent can infer that it modifies an existing destination, but nothing about which destination attributes are updatable or what the operation actually changes.

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 guidance at all on when to use this tool, no prerequisites, and no mention of alternatives such as destination-create for new destinations or destination-one for reading them.

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