Skip to main content
Glama
MCP Dokploy Online
by igoruam

redis-one

Read-onlyIdempotent

Retrieves configuration and status details for a Redis instance by its ID from a Dokploy server.

Instructions

GET /redis.one

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

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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond them — no statement about what the response contains, whether a missing ID errors or returns null, or what permissions are 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 that brevity is under-specification rather than efficiency: two words carry no front-loaded purpose, no scope, and no actionable detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and an undocumented required parameter, the description would need to explain the return shape and identifier semantics. It supplies neither, leaving the definition incomplete for even a simple single-resource fetch.

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% and the only parameter, redisId, is documented nowhere. The description does not explain the identifier's format, where it comes from, or whether it is a UUID, slug, or numeric ID, so the agent has zero guidance on the single required input.

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?

"GET /redis.one" merely restates the tool name as an HTTP route; it never says in plain language that it retrieves a single Redis instance, nor what "one" distinguishes from the sibling redis-search. Only the implicit GET verb hints at a read.

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 prerequisite guidance of any kind. The agent must guess from the name alone that this fetches one instance by ID rather than listing or searching.

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