Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-stop

Idempotent

Stops a running Redis instance in Dokploy using its Redis ID, halting the service while preserving its configuration for later restart.

Instructions

POST /redis.stop

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

Input Schema

NameRequiredDescriptionDefault
redisIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the endpoint path: it does not say whether data is flushed, whether the container is preserved, or what state the instance ends in after stopping.

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 is under-specification rather than conciseness – a bare HTTP route with no front-loaded statement of effect. Nothing is wasted because almost nothing is said.

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 mutation tool with no output schema, zero parameter documentation, and only partial annotations, the description should explain the effect of stopping and the identifier's meaning. It provides none of that, leaving the agent to guess.

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 coverage is 0% and the single required parameter redisId is undocumented in both schema and description. The description does not clarify that redisId identifies the target instance or what format it takes, so it fails to compensate for the coverage gap.

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.stop" – it restates the tool name and HTTP method rather than stating in words that it stops a Redis instance. An agent can infer the purpose from the name, but the description itself adds no verb+resource statement or scope.

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 guidance, no prerequisites, and no mention of alternatives such as redis-start or redis-changeStatus. The agent gets nothing about when stopping is appropriate versus restarting or removing.

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