Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-getDefaultCommand

Read-onlyIdempotent

Returns the default command for a specified Dokploy compose service using its compose ID, so you can verify or reuse the configured startup command.

Instructions

GET /compose.getDefaultCommand

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

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=true, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds nothing beyond the HTTP verb, which duplicates the readOnly hint; it does not say what the default command represents, whether it can be null, or what it is used for.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single short line with no filler, which technically satisfies conciseness and is trivially front-loaded. However, it reads as an auto-generated endpoint stub rather than a deliberate summary, so brevity here reflects missing content rather than tight editing.

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 parameter documentation, and no explanation of the returned default command, an agent has essentially nothing to reason with before calling. For a tool whose semantics are non-obvious from the name, this is completely inadequate.

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, so the description must compensate and does not. There is no indication of what identifier composeId is, what format it takes, or whether it refers to a compose name, service, or deployment.

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?

"GET /compose.getDefaultCommand" mostly restates the tool name and HTTP method rather than stating what the tool returns or what a "default command" is in this domain. It signals a read operation on a compose, but nothing distinguishes it from sibling server-getDefaultCommand or explains the resource being fetched.

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 prerequisites, and no mention of when an agent should prefer this over server-getDefaultCommand or compose-one. The agent must infer everything from the name 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