Skip to main content
Glama
Sign In
mcp-redis-allowlist

mcp-redis-allowlist

by TeaBambooNGU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

redis_command

Execute a Redis command from a configurable read-only allowlist for safe production diagnostics, with optional write access when enabled.

Instructions

Run an arbitrary Redis command restricted to the read-only allowlist unless writes are enabled.

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": {
      "command": "<command>"
    },
    "name": "redis_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It discloses the access control (read-only allowlist, writes optionally enabled) but omits other behaviors: error handling (e.g., denied command), return format, rate limits, or state changes when writes are enabled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core behavior. However, it uses the uncommon spelling 'allowlist' and could be slightly clearer about the write-enabling condition.

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?

Given the complexity of running arbitrary commands and the lack of output schema or parameter descriptions, the description is too sparse. It does not explain expected inputs, outputs, or error scenarios, making it insufficient for reliable agent use.

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 description does not clarify the purpose or format of the 'command' and 'args' parameters. An agent has to infer that 'command' is a Redis command string and 'args' are its arguments, but no examples or constraints are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs an arbitrary Redis command, with a specific restriction to a read-only allowlist unless writes are enabled. This distinguishes it from sibling tools like redis_get (specific commands) by offering a generic runner.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (for commands not covered by siblings) by mentioning the allowlist restriction, but it does not explicitly advise against using it for commands that have dedicated tools or specify prerequisites for enabling writes.

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