Dokploy MCP Server

registry-one

Read-onlyIdempotent

Retrieve a specific registry's details by its ID.

Instructions

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

Input Schema

Name	Required	Description	Default
`registryId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.1Jun 13, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=true, idempotentHint=true, and openWorldHint=true, which convey basic safety and idempotency. However, the description adds no additional behavioral context such as what happens if the registryId does not exist, or whether the tool returns a success response or error. No contradiction with annotations.

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?

While the description is short (one sentence), it is under-specified rather than concise. It omits essential information about the tool's function, parameters, and usage. A good concise description would include the purpose and key parameter details in a compact form.

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?

Given the tool has one required parameter and no output schema, the description should at minimum state that it retrieves a registry entry by ID. The current description is entirely inadequate for an agent to understand the tool's purpose, preconditions, or return value.

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 input schema's 'registryId' parameter has no description, and schema description coverage is 0%. The tool description does not explain what 'registryId' represents or how to obtain it. The parameter semantics are left entirely to the agent to infer from the name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is merely 'GET /registry.one', which is a tautology of the tool name. It does not state that the tool retrieves a specific registry by its ID, nor does it clarify what 'registry' refers to. It fails to distinguish from sibling tools like 'registry-all' 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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus its siblings. For example, it does not explain that this tool is for fetching a single registry entry while 'registry-all' lists all registries, or that 'registry-create' is for creating a new one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server