Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerImage-getImages

Read-onlyIdempotent

Retrieves Docker images available on a Dokploy server so you can inspect image names and IDs for deployment or management tasks. Use the optional serverId to target a specific server.

Instructions

GET /dockerImage.getImages

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": "dockerImage-getImages"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 of its own — no note that listing is unfiltered, no statement about environment/server targeting, and no sense of result size or pagination. It does not contradict the annotations, but it contributes nothing beyond them.

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 single line is not bloated, but it is under-specified rather than concise: there is no front-loaded statement of purpose or scope for an agent to anchor on. Brevity here reflects missing content, not 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?

A listing tool with an open-world read, an undocumented optional parameter, and no output schema requires the description to explain what comes back and how scope is selected. The definition supplies none of that, leaving the agent unable to call it confidently beyond passing no arguments.

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% for the single optional parameter serverId, so the description is the only place meaning could be supplied — and it says nothing. Whether serverId scopes results to a specific Docker endpoint, and what happens when it is omitted, is left entirely undocumented.

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?

"GET /dockerImage.getImages" only restates the endpoint encoded in the tool name; it does not say in prose what a Docker image listing contains or what scope it covers. It hints at a read of images, but an agent gains nothing it could not derive from the name alone, and no differentiation from siblings like dockerImage-getImageConfig is offered.

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 mention of prerequisites (e.g., a reachable Docker server), and no pointer to alternatives such as dockerImage-getImageConfig or dockerDiskUsage-getDiskUsage. The agent must infer applicability entirely from the endpoint string.

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