Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-saveEnvironment

Idempotent

Save environment variables for a Dokploy Compose service and optionally create the env file so deployments use the correct configuration.

Instructions

POST /compose.saveEnvironment

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>",
      "env": "<env>"
    },
    "name": "compose-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
composeIdYes
createEnvFileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare openWorldHint=true and idempotentHint=true; there is no readOnly or destructive signal, so the description carries the burden of disclosing that this is a mutating save. It discloses nothing about overwrite semantics, whether an existing env is replaced, or what the returned result looks like. The route restatement adds zero behavioral context.

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 is under-specification rather than conciseness: a bare HTTP route gives the reader nothing to front-load. Brevity here is a defect, not an efficiency.

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 3-parameter mutating tool with no output schema and no annotation coverage of write semantics, the definition is wholly inadequate. Nothing an agent needs in order to call it correctly — env format, createEnvFile behavior, sibling differentiation — is present.

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 three parameters (composeId, env, createEnvFile), and the description adds no meaning: the format of 'env' (raw string? newline-delimited? JSON?), the identifier source for composeId, and the effect of createEnvFile are all undocumented. The agent cannot tell whether env is a file path or file contents — a critical ambiguity.

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 HTTP route 'POST /compose.saveEnvironment', which restates the tool name rather than explaining what saving an environment actually does (persist env vars? write an .env file?). There is no verb-plus-resource statement beyond what the identifier already tells the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance at all about when to call this instead of the many siblings such as application-saveEnvironment, environment-update, or environment-create. The agent must infer from the name alone that this is the compose-scoped variant.

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