Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-move

Idempotent

Moves a Redis instance to a different Dokploy environment by specifying its ID and the target environment ID.

Instructions

POST /redis.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "redis-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
redisIdYes
targetEnvironmentIdYes

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 supply idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond that—no indication of whether the move causes downtime, migrates data, changes connection endpoints, or requires the target environment to be empty.

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 short, but that brevity reflects under-specification rather than economy—the single fragment conveys no information an agent could act on. There is no front-loaded statement of purpose or effect.

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?

For a two-required-parameter mutation tool with no output schema and minimal annotations, the description is wholly inadequate. An agent cannot determine what the call does, what it returns, or what side effects to expect.

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?

Both required parameters (redisId, targetEnvironmentId) have 0% schema description coverage, and the description does not mention either one. It fails entirely to compensate for the schema gap by explaining formats, ID sources, or constraints on the target environment.

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.move" merely restates the tool name and HTTP method rather than describing what moving a Redis instance entails (e.g., migrating it to another environment). It gives no basis for distinguishing this from sibling tools like application-move, compose-move, or mariadb-move.

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?

The description contains no when-to-use guidance, no prerequisites, and no mention of alternatives such as redis-update or redis-create. An agent has no signal for choosing redis-move over the other -move variants.

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