Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-getConvertedCompose

Read-onlyIdempotent

Retrieves the converted Docker Compose configuration for a specified compose ID, enabling inspection of the generated file before deployment.

Instructions

GET /compose.getConvertedCompose

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

Input Schema

NameRequiredDescriptionDefault
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 already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered; the description adds nothing beyond that. It does not disclose what the conversion does, whether it has side effects, what permissions are needed, or what form the result takes — all of which matter for a tool with openWorldHint true.

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 only because it is under-specified rather than economical — a bare HTTP verb plus route is not a useful, front-loaded explanation of the tool's purpose.

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 tool whose semantics (what "converted" means) are entirely non-obvious, the definition gives an agent nothing to act on: no output expectations, no parameter meaning, no usage context, and no output schema to fall back on.

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 required parameter composeId, and the description provides no clarification of its format or meaning. With one undocumented parameter, the description fully fails to compensate for the schema gap.

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 raw endpoint string "GET /compose.getConvertedCompose", which essentially restates the tool name. It never explains what a "converted compose" is — converted into what, from what source, or for what purpose — nor how it differs from siblings like compose-one or compose-getDefaultCommand.

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 preconditions, and no mention of any alternative tool. An agent has no basis for choosing this over compose-one or compose-getDefaultCommand.

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