Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-update

Idempotent

Updates an existing Dokploy container registry by ID, letting you change its name, URL, type, credentials, or image prefix to correct connection details or rotate access.

Instructions

POST /registry.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": {
      "registryId": "<registryId>"
    },
    "name": "registry-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordNo
serverIdNo
usernameNo
createdAtNo
registryIdYes
imagePrefixNo
registryUrlNo
registryNameNo
registryTypeNo
organizationIdNo

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 idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond that: it does not say whether it is a full or partial update, which fields are mutable, whether credentials or permissions are required, or how omitted fields are treated.

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 brevity here reflects under-specification rather than efficiency. A bare HTTP verb-plus-path fragment is not front-loaded explanatory structure an agent can act on.

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?

A 10-parameter mutation tool with no parameter documentation, no output schema, and thin annotations needs a substantive description. One endpoint string cannot tell an agent how to construct a correct update request or what will happen to the registry.

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 schema has 10 parameters with 0% description coverage, including credential fields (username, password) and an anyOf/null imagePrefix. The description supplies no meaning for any parameter, so it fails to compensate for the complete absence of schema documentation.

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 endpoint string "POST /registry.update", which essentially restates the tool name with an HTTP verb. It conveys that some registry resource is modified, but not what the operation actually changes, and it does nothing to separate this from registry-create or registry-one.

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 tool versus its siblings such as registry-create, registry-one, or registry-remove. The only implicit signal is the word "update" and the POST method, leaving the agent to infer that this is the mutation path for existing registries.

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