Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-create

Creates a Redis database instance in a Dokploy environment using a required name, environment ID, and password, enabling applications to provision data storage.

Instructions

POST /redis.create

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": {
      "name": "<name>",
      "databasePassword": "<databasePassword>",
      "environmentId": "<environmentId>"
    },
    "name": "redis-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
descriptionNo
dockerImageNoredis:8
environmentIdYes
databasePasswordYes

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 only a title and openWorldHint=true, so the description carries the full burden and delivers nothing: no statement that this is a mutating, billable provisioning call, whether the password is stored or returned, what happens on name collision, or how long creation takes. None of the side effects an agent needs before committing a write are disclosed.

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 this is under-specification rather than conciseness: four words convey no information an agent could act on. There is no front-loaded statement of purpose to anchor the rest of the definition.

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 7-parameter provisioning tool with only minimal annotations and no output schema, the description should explain required inputs, defaults, and the result of the call. It explains none of these, leaving the definition effectively undocumented.

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% across 7 parameters, and the description adds no meaning for any of them. Critical ambiguities go unaddressed, notably appName vs name vs serverId, the dockerImage default of redis:8, and how databasePassword is handled after creation.

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.create" only restates the tool name and its HTTP method; there is no plain-language statement of what is provisioned. An agent must infer 'creates a Redis instance' from the operation id alone, and nothing distinguishes it from redis-deploy, redis-rebuild, or the other *-create 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 guidance on when to use this versus redis-deploy, redis-rebuild, or any other lifecycle sibling, and no prerequisites such as an existing environment or credentials. The description is a route stub, so any routing decision falls entirely on the caller's prior knowledge.

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