Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-templates

Read-onlyIdempotent

Fetch Docker Compose templates from a Dokploy instance to review available stacks and choose one for deployment.

Instructions

GET /compose.templates

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compose-templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseUrlNo

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 carried structurally. The description adds nothing beyond that — no indication of what the listing returns, whether it is filtered, paginated, or scoped to a team/organization.

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, but that brevity comes from under-specification rather than economy — a raw route string is not a front-loaded explanation of behavior. No sentence earns its place because no explanatory sentence exists.

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 and an undocumented parameter, the description carries the full burden of explaining results and scope, and it provides none. An agent cannot tell what a 'compose template' object looks like or how large the response is.

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?

There is one parameter (baseUrl) with 0% schema description coverage, so the description is the only place its meaning could be explained, and it says nothing. The endpoint string gives no hint about what baseUrl targets or whether it is optional in practice.

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 raw endpoint string "GET /compose.templates", which essentially restates the tool name. An agent can infer 'list compose templates' only by parsing the HTTP verb and path, not from any stated verb+resource description, and nothing distinguishes it from siblings like user-getBookmarkedTemplates or compose-previewTemplate.

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 on when to use this tool, when not to, or which sibling to prefer. The many template-related siblings (previewTemplate, deployTemplate, processTemplate, getTags) are left with no routing information at all.

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