Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-reload

Idempotent

Reload a Redis instance's configuration in Dokploy to apply changes without recreating the service.

Instructions

POST /redis.reload

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>",
      "appName": "<appName>"
    },
    "name": "redis-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
redisIdYes

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 supply openWorldHint=true and idempotentHint=true, so the safety profile is at least partially covered, but the description adds nothing beyond the route string — no statement about service disruption, config re-read semantics, required auth, or failure modes. For a mutating endpoint named 'reload', the lack of any disclosure about what changes take effect is a real 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?

It is short, but shortness here reflects under-specification rather than economy — a single route string with no front-loaded purpose statement. There is nothing to trim because there is essentially nothing there.

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?

This is a two-required-parameter mutating endpoint with no output schema and zero schema coverage; the description should carry the explanatory load but supplies only an HTTP method and path. Nothing an agent needs in order to invoke it correctly is present.

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% and both parameters (redisId, appName) are required with no descriptions, bounds rationale, or format hints. The description does not compensate in any way, so an agent cannot infer what redisId refers to or whether appName scopes the reload.

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.reload', which restates the tool name rather than explaining what the operation does. It conveys the transport method but gives no resource-level meaning (e.g. reloading configuration vs. restarting the process) that would distinguish it from redis-start, redis-rebuild, or the other *-reload siblings.

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 at all: no prerequisites, no conditions that select this over redis-rebuild or redis-start, and no note about whether the target service must already be running. 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