Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getConfig

Read-onlyIdempotent

Retrieves the Docker configuration for a specified container by its container ID, enabling inspection of runtime and deployment settings on Dokploy.

Instructions

GET /docker.getConfig

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": {
      "containerId": "<containerId>"
    },
    "name": "docker-getConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
containerIdYes

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?

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered without the description. The description contributes nothing beyond that: no note on whether the config requires a running container, whether it exposes secrets/env vars, or what happens with an unknown containerId.

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 short because it is under-specified rather than distilled. There is no front-loaded statement of purpose, only a path-like string.

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 0% schema coverage, no output schema, and no annotations explaining what is returned, the description leaves the agent without enough information to call this tool confidently or interpret its result.

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 says nothing about either parameter. The required containerId and the optional serverId (likely a Docker host selector) are documented nowhere, so an agent must guess at their meaning and format.

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 /docker.getConfig" restates the tool name as a pseudo-endpoint and only adds the HTTP verb GET, which hints at a read. It never says what a Docker container config is, or what scope of configuration is returned for the given container.

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 alternatives such as the sibling config readers (dockerImage-getImageConfig, dockerVolume-getVolumeConfig). An agent has no basis to choose this tool over them.

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