Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-start

Idempotent

Start a stopped Redis instance in Dokploy by supplying its Redis ID to resume service availability.

Instructions

POST /redis.start

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

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 already declare openWorldHint=true and idempotentHint=true, so the description only needs to add context — yet it adds nothing about side effects, whether the call blocks until the instance is ready, what happens when the instance is already running, or permission requirements. The endpoint string confirms a mutation but conveys no behavior beyond that.

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 comes from under-specification rather than economy: a raw HTTP route is not a helpful front-loaded statement of intent.

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?

A state-changing lifecycle tool with an undocumented required parameter, no output schema, and only sparse annotations lacks virtually everything an agent needs to invoke it confidently. The definition offers no lifecycle semantics, no preconditions, and no result expectations.

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 the single required parameter redisId, so the description must explain what identifier form is expected (instance ID vs. name) and it does not. No meaning is added beyond the bare schema type.

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.start" restates the tool name and HTTP route without saying what starting a Redis instance actually entails (provisioning? resuming a stopped instance?). It hints at a verb+resource but gives no basis for distinguishing it from siblings like redis-deploy, redis-reload, or redis-rebuild.

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, and no mention of alternatives such as redis-stop, redis-deploy, or redis-reload. The agent must infer usage entirely from the tool 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