Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveEnvironment

Idempotent

Saves an application's environment variables, build arguments, build secrets, and env-file creation setting to persist configuration changes.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>",
      "env": "<env>",
      "buildArgs": "<buildArgs>",
      "buildSecrets": "<buildSecrets>",
      "createEnvFile": "<createEnvFile>"
    },
    "name": "application-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
buildArgsYes
buildSecretsYes
applicationIdYes
createEnvFileYes

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 supply idempotentHint=true and openWorldHint=true, but the description adds no behavioral context: it does not say whether existing env content is overwritten, what permissions are needed, or what createEnvFile does on disk. Only the bare 'POST' hints that this is a write operation, which is thin beyond the structured data.

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?

There is no wasted wording, but that is because there is essentially no content. The single route fragment is under-specification rather than conciseness and conveys nothing an agent could act on.

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?

A five-parameter, fully-required mutation with no output schema and no annotation covering destructiveness demands substantive description. This definition provides none, leaving an agent unable to invoke it correctly.

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% and all five parameters are required, yet the description says nothing about applicationId, env, buildArgs, buildSecrets, or createEnvFile. Format (e.g., raw dotenv text vs JSON), encoding, and expected shape of the string-or-null fields are entirely undocumented.

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 /application.saveEnvironment', which restates the tool name plus its transport rather than explaining what saving an environment means. Nothing states that it writes env variables, build args, build secrets, or an env file, so an agent cannot distinguish its effect from siblings like environment-update or environment-create.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. An agent has no basis to choose this over environment-update, environment-create, or compose-saveEnvironment from the text 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