Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-changePassword

Idempotent

Updates the password for a specified Redis instance using its ID and a new password, enabling credential rotation for managed Redis services.

Instructions

POST /redis.changePassword

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>",
      "password": "<password>"
    },
    "name": "redis-changePassword"
  }
}

Input Schema

NameRequiredDescriptionDefault
redisIdYes
passwordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations only declare openWorldHint and idempotentHint; the description adds nothing about consequences such as existing connections being dropped, whether a restart occurs, or permission requirements. For a credential-changing mutation with no annotation coverage of safety or side effects, this is a major gap.

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 description is a single uninformative route string with no structure, no front-loaded intent explanation, and no supporting detail. Brevity here is under-specification rather than conciseness.

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?

A mutating, open-world password change with two undocumented required parameters and no output schema requires the description to carry the behavioral and parameter burden, and it provides none of it. An agent could invoke it but cannot predict its effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 that redisId identifies the target instance or what constraints apply to the password (length, complexity, whether existing sessions stay valid).

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.changePassword", which essentially restates the tool name. It implies a password mutation on a Redis instance but never states what changes or for whom, and gives no differentiation from sibling changePassword tools beyond the 'redis' prefix already in the name.

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 (e.g. instance must be running, credentials required), and no mention of alternatives such as redis-update. The agent gets no signal about when this is the right call.

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