Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-deploy

Idempotent

Deploys a Redis service instance in Dokploy using its ID, enabling Redis provisioning through the MCP server.

Instructions

POST /redis.deploy

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

Input Schema

NameRequiredDescriptionDefault
redisIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations supply openWorldHint=true and idempotentHint=true, so idempotency and external reach are already declared. The description adds only the HTTP verb, which hints at a mutating call, but it does not say what deploy does to an existing instance (redeploy, restart, recreate), whether data is preserved, or what authorization is needed.

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 brevity here is under-specification rather than conciseness. A route string is not a useful front-loaded statement of intent for an agent.

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?

Deploy is a consequential mutation with no output schema and no annotation covering destructiveness, yet the description provides no information about effect, reversibility, or result. Nothing an agent needs to call this safely is present.

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 redisId parameter, so the burden falls on the description. It says nothing about the identifier's meaning (instance ID vs. name) or accepted format, leaving the schema's bare type as the only guidance.

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 the raw route string "POST /redis.deploy", which essentially restates the tool name in HTTP form. It conveys that a Redis resource is being deployed, but no scope, target state, or effect is stated, so it does not distinguish this from siblings like redis-start, redis-rebuild, or redis-create.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 exclusions. Given siblings such as redis-start, redis-rebuild, redis-create, and redis-reload, the agent is left to guess which operation applies in a given situation.

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