Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-processTemplate

Idempotent

Process a base64-encoded Docker Compose template for a specified compose ID to apply configuration changes to a Dokploy deployment.

Instructions

POST /compose.processTemplate

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>",
      "composeId": "<composeId>"
    },
    "name": "compose-processTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64Yes
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations declare openWorldHint=true and idempotentHint=true but say nothing about safety, side effects, or auth, and the description adds zero context beyond the route. Critically, nothing indicates what the call creates or mutates, what the base64 payload represents, or why a 'process' POST would be idempotent.

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 this is under-specification rather than conciseness; there is no front-loaded statement of purpose. A route fragment alone does not earn its place as a tool description.

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 two-required-parameter mutating endpoint with no output schema and no parameter documentation, the definition supplies none of the information an agent needs. It is inadequate on every axis: purpose, inputs, effects, and return behavior.

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?

Both required parameters (base64, composeId) have 0% schema description coverage, so the description carries the full burden and provides nothing. It never explains that base64 is presumably an encoded template file, nor how composeId relates to the processed template.

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 HTTP route "POST /compose.processTemplate", which restates the tool name in path form. It does convey an HTTP verb and resource for a templating endpoint, but it never says what 'process' actually does (create a compose from a template? convert? deploy?), so it cannot be distinguished from siblings like compose-previewTemplate 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 or when-not-to-use guidance whatsoever; the string contains no natural-language sentence. An agent has no basis to choose this over compose-previewTemplate, compose-deployTemplate, or compose-import based on the definition text alone.

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