Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-changeStatus

Idempotent

Changes a Dokploy Redis service status to idle, running, done, or error using the specified Redis ID.

Instructions

POST /redis.changeStatus

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>",
      "applicationStatus": "<applicationStatus>"
    },
    "name": "redis-changeStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
redisIdYes
applicationStatusYes

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 only declare openWorldHint=true and idempotentHint=true, with no readOnly/destructive hints. The description supplies nothing beyond them: it doesn't say whether the change is reversible, what happens to running workloads when status is set to idle or error, whether the instance must be stopped first, or what the response looks like. It does not contradict the annotations, but behavior for a mutation-style call remains largely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single terse HTTP-method-plus-path fragment. It is short, but under-specified rather than concise, and there is no informative content front-loaded because none exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-required-parameter mutation tool with no output schema and no schema description coverage, the description should explain the status lifecycle and side effects. It provides none, leaving the agent to guess at enum semantics and consequences of the call.

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% with two required parameters (redisId, applicationStatus). The description says nothing about either – not the redisId format, nor the operational meaning of each enum value (idle, running, done, error) or which transitions are legal. Zero added meaning beyond the bare schema.

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 just "POST /redis.changeStatus" – it restates the endpoint and tool name without explaining what a status change means for a Redis resource. Only the name hints that it mutates application status; the description text itself adds nothing. Differentiation from sibling *-changeStatus tools comes entirely from the resource prefix in the name, not from the description.

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 prerequisite information is given. With siblings like redis-start, redis-stop, redis-rebuild, and redis-remove, an agent cannot tell from this description when a status change is appropriate versus those alternatives.

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