Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-saveEnvironment

Idempotent

Saves environment variables for a Redis instance in Dokploy using its ID, so you can update Redis configuration without manual edits.

Instructions

POST /redis.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": {
      "redisId": "<redisId>",
      "env": "<env>"
    },
    "name": "redis-saveEnvironment"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
redisIdYes

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 already declare idempotentHint=true and openWorldHint=true, so the description is not the sole source of behavioral information. However, it adds zero context of its own — nothing about whether existing environment variables are replaced or merged, what format 'env' takes, or what the response contains for a mutation of this kind.

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?

The single line is short but wastes its only words on the HTTP method and route, which duplicate transport-level information. Brevity here is under-specification, not 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?

This is a mutation-style tool with two undocumented required parameters, no output schema, and only weak annotation coverage, yet the description supplies no operational detail at all. An agent cannot reliably construct a correct call from this definition.

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 both required parameters, so the description must compensate and does not. It never explains what 'redisId' identifies or what structure the 'env' string must contain (dotenv lines, JSON, key=value pairs), leaving an agent to guess a critical input format.

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 /redis.saveEnvironment", which restates the tool name rather than explaining what saving an environment means. An agent can infer 'write environment data for a Redis service' from the name alone, but the description contributes nothing beyond it and does not distinguish this from siblings like environment-update or compose-saveEnvironment.

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 prerequisite or scoping conditions, and no mention of any alternative tool. The description gives an agent no basis for choosing this over redis-update, environment-update, or the per-engine saveEnvironment siblings.

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