Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerImage-getImageConfig

Read-onlyIdempotent

Fetch Docker image configuration by image reference, optionally with a server ID, to inspect image settings before deployment.

Instructions

GET /dockerImage.getImageConfig

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": {
      "imageRef": "<imageRef>"
    },
    "name": "dockerImage-getImageConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageRefYes
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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. The description adds no behavioral context at all: it does not say whether the image must already exist locally, whether it triggers a registry pull, or what happens when imageRef cannot be resolved.

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 technically short with no filler, but the single line is an under-specified route echo rather than a front-loaded explanation, so brevity here is a liability rather than efficiency.

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?

With two undocumented parameters, no output schema, and no explanation of the returned config shape, the description leaves an agent unable to construct a correct call or anticipate the result. Everything an agent needs must be guessed from the name alone.

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?

Schema description coverage is 0% and the description supplies zero parameter meaning. It never explains the required imageRef format (name, name:tag, or digest) or what serverId selects when multiple Docker servers are configured.

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 "GET /dockerImage.getImageConfig", which restates the tool name and HTTP method rather than explaining what an image config actually contains or why an agent would fetch it. It gives no differentiation from the closely named sibling docker-getConfig or from dockerImage-getImages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 preconditions, and no mention of alternatives such as docker-getConfig. An agent must infer entirely from the tool name whether this applies to a specific image reference versus a server-wide config.

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