Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-one

Read-onlyIdempotent

Retrieve details for a single Docker Compose deployment by composeId from a connected Dokploy instance.

Instructions

GET /compose.one

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

Input Schema

NameRequiredDescriptionDefault
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 what is returned, whether a missing ID errors or returns null, or whether unknown fields are ignored.

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 technically concise, but the brevity comes from under-specification rather than economy — a bare route string with no front-loaded statement of purpose. There is nothing to restructure because there is essentially no content.

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 with one undocumented required parameter and no output schema, the description should carry the full explanatory burden, and it carries none. An agent cannot tell what the response looks like or how to source the composeId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter, composeId, has zero schema description coverage and the description does not mention it at all. The name only weakly implies the ID identifies the compose to fetch; there is no detail on format, source, or where an agent obtains a valid value.

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.one", which restates the tool name in HTTP form. An agent can infer it retrieves a single compose resource, but there is no statement of what a 'compose' is here or how this differs from siblings like compose-search or compose-getConvertedCompose beyond the name.

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 at all about when to use this tool, when not to, or which sibling to prefer (e.g., compose-search for lookups by other criteria). 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