Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-remove

Destructive

Deletes a specified Redis instance from Dokploy by its ID, so you can clean up unused database resources.

Instructions

POST /redis.remove

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

Input Schema

NameRequiredDescriptionDefault
redisIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the endpoint string: no note on irreversibility, data loss, confirmation requirements, or dependent resources. It does not contradict the annotations, but it is empty of behavioral context.

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?

The text is short, but brevity here is under-specification rather than conciseness; it is raw routing metadata with no front-loaded purpose statement. Nothing is wasted, but nothing useful is conveyed either.

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 destructive, open-world mutation with an undocumented required identifier and no output schema, the definition should explain at minimum the target resource and the identifier. None of that 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?

The single parameter redisId has 0% schema description coverage, so the description carries the full burden of explaining it—and it says nothing. There is no indication of identifier format, source, or whether it is a name or numeric ID.

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.remove" only restates the tool name and HTTP method; it never states in prose that it deletes a Redis instance or what that entails. An agent can guess the resource from the name, but the description contributes no verb+resource framing of its own.

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, when-not-to-use, or alternative guidance at all. Siblings such as redis-stop, redis-changeStatus, or redis-one are not referenced, even though distinguishing a delete from a stop is exactly the ambiguity an agent faces here.

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