Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-testRegistryById

Idempotent

Tests a configured container registry by ID to verify its connectivity and credentials before deployment.

Instructions

POST /registry.testRegistryById

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "registry-testRegistryById"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
registryIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations supply only openWorldHint=true and idempotentHint=true, so the description carries the burden for safety and side effects and delivers nothing. It never says whether the test contacts an external registry, whether it can mutate stored state (it is a POST), what credentials are needed, or what a failed test looks like; the only signal is the bare HTTP method.

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 it is under-specified rather than concise: a single route string with no front-loaded statement of purpose. There is no information for any sentence to be trimmed from.

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 two-parameter, open-world operation with no output schema and no annotations covering read/write semantics requires far more explanation. Nothing about inputs, side effects, or return behavior 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?

Both parameters have 0% schema description coverage, so the description must explain serverId and registryId semantics, but it says nothing. The reader cannot tell what a serverId scopes or how registryId relates to it.

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 only restates the tool name as an HTTP route ("POST /registry.testRegistryById"). It conveys no verb+resource intent beyond what the name already implies, and does not distinguish it from the sibling 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 prerequisite (e.g., whether the registry must exist first), and no statement of how this differs from registry-testRegistry. An agent must guess based on the name alone.

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