Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-update

Idempotent

Update an existing deployment environment by ID, including its name, description, and environment variables, to keep configuration current.

Instructions

POST /environment.update

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": {
      "environmentId": "<environmentId>"
    },
    "name": "environment-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
nameNo
projectIdNo
descriptionNo
environmentIdYes

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 there is no readOnly or destructive hint, so the mutation profile is unstated. The description adds nothing about which fields are patched, whether omitted fields are cleared, or what permissions are required; the bare "POST" only weakly signals mutation.

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?

Brevity here is under-specification rather than conciseness: a single route fragment with no front-loaded statement of purpose or effect. There is no wasted sentence, but there is also no useful content.

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 mutation tool with zero schema descriptions, no output schema, and sparse annotations is left almost entirely unexplained. Nothing tells the agent what the call returns or how partial updates behave.

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% across five parameters, and the description supplies no meaning for any of them. In particular the relationship between the required environmentId and the optional env/name/projectId/description fields is left 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?

"POST /environment.update" restates the tool name plus an HTTP method; it never says what an environment update does or what it changes. An agent learns only that this is a write endpoint on the environment resource, which the name already conveyed.

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 distinction from siblings such as environment-create, environment-duplicate, or environment-remove. The agent must guess the selection criteria entirely.

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