Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-rebuild

Idempotent

Rebuild a Redis instance in Dokploy by its ID to restore or reset the service after configuration changes or failures.

Instructions

POST /redis.rebuild

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-rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 safety profile is partly covered. The description adds only that the call is an HTTP POST; it omits the risk that matters most for a rebuild — whether persisted data is destroyed, whether there is downtime, and what auth is required.

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 text is short and contains no filler, but that is brevity from under-specification rather than good structure. It front-loads a URL route instead of the useful information an agent needs before invoking the tool.

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 destructive-adjacent mutation tool with no output schema and an undocumented required parameter, the description supplies none of the needed context. There is no return-value hint, no side-effect warning, and no distinction from the many sibling rebuild tools for other databases.

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 coverage is 0% and the single required parameter redisId has no description anywhere. The description does not explain that redisId identifies the target Redis instance, nor its format, nor what happens if it refers to a nonexistent or running instance.

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 "POST /redis.rebuild", which restates the tool name and title in HTTP-path form rather than explaining the action. It does signal a mutating operation on a Redis resource via POST, but an agent learns nothing about what a rebuild actually does (restart from a snapshot, recreate the container, reload config, etc.) or how it differs from siblings like redis-reload or redis-redeploy.

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 preconditions (e.g. instance must be stopped or deployed first), and no mention of alternatives such as redis-reload or redis-update that also mutate the instance. The agent must guess entirely from the name.

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