Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-previewTemplate

Idempotent

Preview a Docker Compose template before deployment using Base64 content and app name; optionally specify a server ID to target a Dokploy server.

Instructions

POST /compose.previewTemplate

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": {
      "base64": "<base64>",
      "appName": "<appName>"
    },
    "name": "compose-previewTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64Yes
appNameYes
serverIdNo

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 already declare openWorldHint=true and idempotentHint=true, so idempotency and external-world reach are covered. The description contributes only the POST method, which hints at a server call but says nothing about whether a preview creates persistent state, requires the template to exist first, or what it returns — notable because no readOnlyHint or destructiveHint is supplied.

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 certainly short, but the brevity reflects under-specification rather than conciseness: a bare endpoint path with no front-loaded purpose statement. Nothing is wasted, but nothing useful is delivered either.

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?

For a three-parameter, zero-coverage, annotation-light tool with no output schema, the description should explain the preview outcome and parameter roles. It does none of that, leaving an agent unable to call the tool correctly without inspecting external API documentation.

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 mentions no parameters, so the meanings of base64, appName, and serverId are undocumented anywhere. The agent cannot tell what base64 encodes (the compose file?), whether appName must match an existing application, or when optional serverId should be supplied.

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 the HTTP route "POST /compose.previewTemplate", which essentially restates the tool name rather than describing what the operation does in plain language. An agent can infer a preview of a compose template from the name alone, but the definition adds no verb-plus-resource explanation and no differentiation from siblings like compose-processTemplate or compose-deployTemplate.

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 at all: no mention of prerequisites, no comparison to compose-deployTemplate or compose-processTemplate, and no indication of whether a preview must precede a deploy. The agent must guess entirely from the 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