Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-create

Create a cloud container registry connection in Dokploy with credentials, URL, and image prefix to enable deployments to pull images from your registry.

Instructions

POST /registry.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": {
      "registryName": "<registryName>",
      "username": "<username>",
      "password": "<password>",
      "registryUrl": "<registryUrl>",
      "registryType": "<registryType>",
      "imagePrefix": "<imagePrefix>"
    },
    "name": "registry-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
serverIdNo
usernameYes
imagePrefixYes
registryUrlYes
registryNameYes
registryTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations supply only a title and openWorldHint=true, so the description carries nearly the full behavioral burden and discloses none of it. It never says this is a mutating create, that credentials (username/password) are stored, whether the registry is validated against a live endpoint, or what happens on name collision.

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 brief but that brevity is under-specification rather than conciseness; there is nothing to front-load because no substantive information is present. It spends its only characters repeating the operation path.

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 7-parameter mutation tool that takes credentials, with no output schema and only an openWorldHint annotation, the definition is wholly inadequate. An agent has no information about request behavior, validation, or results beyond what it must infer from property names.

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 7 parameters, 6 of them required, and the description adds no meaning at all. Key ambiguities — the format of registryUrl, the role of serverId, whether imagePrefix may be null, and why registryType is fixed to "cloud" — are left entirely undocumented.

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 "POST /registry.create", which restates the tool name and HTTP verb rather than stating what the tool does in domain terms. An agent can guess it creates a registry entry, but nothing explains what a registry is here or how this differs from registry-update or registry-testRegistry.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The description offers nothing to help an agent choose between this and the many sibling create/update/test tools.

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