Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-testRegistry

Idempotent

Tests a cloud container registry connection using provided credentials and URL to verify access before configuring deployments.

Instructions

POST /registry.testRegistry

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": {
      "username": "<username>",
      "password": "<password>",
      "registryUrl": "<registryUrl>",
      "registryType": "<registryType>"
    },
    "name": "registry-testRegistry"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
serverIdNo
usernameYes
imagePrefixNo
registryUrlYes
registryNameNo
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 declare openWorldHint=true and idempotentHint=true, but the description adds nothing about the external network call, the credential requirements, or what a successful versus failed test looks like. For a connection-test operation taking a username and password, behavior around auth failure and side effects is entirely undisclosed.

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, but it is under-specified rather than concise: an endpoint string with no sentence structure or front-loaded purpose to guide the agent. Brevity here reflects absent content, not efficient writing.

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 seven-parameter, four-required credential-bearing tool with no output schema and no annotation coverage of safety requires much more explanation than this. Nothing about the registry being tested, the meaning of registryName versus registryUrl, or the expected result is provided.

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?

Seven parameters with 0% schema description coverage and no enum documentation, and the description explains none of them. Critical fields like registryUrl, registryType (constrained to 'cloud'), serverId, and imagePrefix receive no meaning from either the schema or the description.

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.testRegistry', which restates the tool name and HTTP verb without stating what the operation does or what it returns. An agent cannot tell how this differs from registry-testRegistryById beyond guessing from the name.

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 the sibling registry-testRegistryById or when one should be preferred over the other. The agent is left to infer the entire selection decision from tool names.

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