Skip to main content
Glama
MCP Dokploy Online
by igoruam

registry-all

Read-onlyIdempotent

Retrieve all Docker registries configured in a Dokploy instance so you can inspect available registry settings.

Instructions

GET /registry.all

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-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description adds no behavioral context of its own — nothing about result volume, pagination, or whether the listing is filtered by auth scope, which matters especially given openWorldHint=true.

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 that is under-specification, not conciseness — it is a URL fragment rather than a front-loaded sentence describing the operation. No wasted words, but nothing is communicated either.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-parameter list operation, a single sentence stating that it returns all registries (and whether pagination or filtering applies) would be sufficient — and that sentence is absent. There is no output schema, so the description carries the burden of explaining the return, which it does not.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty with full coverage, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4; no parameter meaning is lost.

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 raw route string "GET /registry.all" — a restatement of the tool name rather than a statement of what it does. An agent can guess it lists all registries, but that meaning comes from naming convention, not from the description, and there is no explicit differentiation from siblings like registry-one or ai-getAll.

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 whatsoever about when to call this versus registry-one (single lookup) or the other *-all list tools. No prerequisites, no scope limits, no mention of alternatives — the agent must infer everything from the tool name.

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