Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-loadMountsByService

Read-onlyIdempotent

Loads the volume and bind mount entries for a specific service in a Dokploy compose application using the compose ID and service name to identify the target.

Instructions

GET /compose.loadMountsByService

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>",
      "serviceName": "<serviceName>"
    },
    "name": "compose-loadMountsByService"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes
serviceNameYes

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 safety is covered; the description adds nothing beyond them. It says nothing about what is returned, whether missing services error or return empty, or how mounts relate to compose services.

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 a single short line with no wasted words, but that brevity comes from under-specification rather than efficiency. There is no front-loaded statement of purpose for the agent to anchor on.

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, two undocumented required parameters, and no behavioral notes, the definition leaves an agent unable to know what a call returns or how to form valid identifiers. The endpoint string alone is inadequate for invocation.

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 parameters (composeId, serviceName) have zero schema description coverage, so the description carries the full burden of explaining them, and it explains none of them. No formats, identifier sources, or expected shapes are given.

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 verb plus the operation name in dotted form ("GET /compose.loadMountsByService"), which restates the tool name rather than stating in plain language what it does. An agent can infer it loads mounts for a compose service, but nothing is articulated about the resource returned or its scope.

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 exclusions, and no mention of an alternative despite a closely related sibling such as mounts-listByServiceId. The agent has no signal for choosing between this and other mount-listing tools.

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