Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-fetchSourceType

Idempotent

Fetches the source type for a specified Docker Compose resource by compose ID, helping you determine how it is deployed.

Instructions

POST /compose.fetchSourceType

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

Input Schema

NameRequiredDescriptionDefault
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 declare openWorldHint=true and idempotentHint=true but say nothing about read vs write or side effects; the description adds only the word POST, which hints at a mutation while the idempotent annotation is left unexplained. It discloses nothing about what is affected, permissions required, or what comes back.

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 with no wasted words, but that brevity reflects under-specification rather than discipline; the single line carries no actionable content beyond the endpoint path.

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 an undocumented required identifier, no output schema, and only sparse annotations, the description is entirely inadequate. An agent cannot determine what the call does, what it returns, or when it should be used.

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 supplies no meaning, format, or example for it. With low coverage the description is expected to compensate, and it does not.

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 an HTTP route stub, "POST /compose.fetchSourceType", which restates the tool name rather than explaining what source type is fetched or what the operation returns. An agent learns the transport method but not the semantic purpose, and there is no differentiation from siblings like compose-one or compose-loadServices.

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 any alternative tool. The agent must guess the scenario that selects this endpoint over the many other compose-* 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