Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-update

Idempotent

Update an existing Redis service's configuration in Dokploy, including image, environment variables, limits, replicas, and network or swarm settings, to match current deployment needs.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
envNo
argsNo
nameNo
appNameNo
commandNo
redisIdYes
cpuLimitNo
replicasNo
createdAtNo
modeSwarmNo
networkIdsNo
descriptionNo
dockerImageNo
labelsSwarmNo
memoryLimitNo
externalPortNo
networkSwarmNo
ulimitsSwarmNo
environmentIdNo
cpuReservationNo
placementSwarmNo
databasePasswordNo
healthCheckSwarmNo
applicationStatusNo
endpointSpecSwarmNo
memoryReservationNo
updateConfigSwarmNo
restartPolicySwarmNo
rollbackConfigSwarmNo
detachDokployNetworkNo
stopGracePeriodSwarmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already state idempotentHint=true and openWorldHint=true, yet the description adds nothing beyond the HTTP method. For a 31-parameter mutation it omits whether this is a full replace or partial patch, what fields are destroyed when omitted, permission requirements, and any deployment side effects.

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 brief, but that brevity is under-specification rather than economy; a bare endpoint string carries no front-loaded information an agent can 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?

Given 31 parameters, nested Swarm configuration objects, a single required redisId, and no output schema, the description is wholly inadequate for calling the tool 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% across 31 parameters, including opaque nested Swarm objects (placementSwarm, updateConfigSwarm, endpointSpecSwarm), and the description supplies no parameter meaning whatsoever. The burden of explanation is entirely unmet.

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 /redis.update" merely restates the tool name plus an HTTP verb; it never says what an update to a Redis resource actually changes. An agent cannot distinguish it from siblings like redis-create, redis-deploy, or redis-changePassword without inferring from the name alone.

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 mention of alternatives such as redis-create for new resources. The only signal is the word "update" in the endpoint path.

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