Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-one

Read-onlyIdempotent

Retrieves a specific registry configuration by ID so you can inspect or manage it within a Dokploy instance.

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

NameRequiredDescriptionDefault
registryIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the route string: it does not say what is returned, whether a missing ID errors, or what openWorld access implies.

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 that brevity reflects under-specification rather than conciseness. A raw route string is not front-loaded with any useful information.

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 tool with one undocumented parameter, no output schema, and no explanatory text, the definition is inadequate. An agent cannot tell what a successful call returns or how to handle an unknown registryId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter registryId has 0% schema description coverage, and the description does not compensate by explaining its format or meaning. The agent learns only that some registryId string is required.

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 just the HTTP route "GET /registry.one", which restates the tool name rather than stating what the tool does. It does not say whether it fetches a single registry by ID, and it does not distinguish this tool from the sibling registry-all.

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 on when to use this tool versus registry-all or registry-testRegistryById. The agent must infer from the name alone that this retrieves one registry.

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