Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-loadServices

Read-onlyIdempotent

Loads the services defined in a Dokploy compose stack by compose ID, with optional cache or live fetch, so you can inspect stack components before managing or deploying them.

Instructions

GET /compose.loadServices

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-loadServices"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNocache
composeIdYes

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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that – no note on whether the result is cached, when a fresh fetch occurs, or what happens if the compose does not exist.

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?

One line, so nothing is wasted, but it is under-specified rather than concise; there is no front-loaded purpose statement to structure the reader's understanding.

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 no output schema, no annotation-adjacent explanation, and 0% parameter documentation, the definition leaves the return shape, the cache/fetch semantics, and error behavior entirely unaddressed for a tool whose output the agent must interpret.

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 two parameters, and the description does not mention either. In particular the 'type' enum (fetch vs cache) with default 'cache' is a behaviorally important switch left completely unexplained, and composeId's format is 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?

The description is an HTTP endpoint restatement, 'GET /compose.loadServices', which essentially echoes the tool name. It gives no verb-plus-resource statement the agent could not already derive from the name, and does not indicate whether it returns the list of services in a compose project or triggers a load operation.

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 guidance about when to use this tool versus alternatives such as compose-loadMountsByService or overview-services, nor any mention of prerequisites, exclusions, or the meaning of the cache/fetch choice.

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