Skip to main content
Glama
Sign In
AI Data MCP

AI Data MCP

by ResetFull
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run read-only Redis command

redis_command
Read-onlyIdempotent

Execute one allowlisted read-only Redis command with tokenized arguments; mutations and risky operations like KEYS, scripting, pub/sub, and transactions are rejected.

Instructions

Run one explicitly allowlisted read-only Redis command with tokenized arguments. KEYS, scripting, administration, pub/sub, transactions, blocking operations, and all mutations are rejected.

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

Input Schema

NameRequiredDescriptionDefault
argumentsYesRedis command name followed by already-tokenized arguments. Do not pass one shell-style command string.
connection_idYes
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-alpha.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real value beyond them by disclosing the explicit allowlist posture and enumerating what is rejected (KEYS, scripting, pub/sub, transactions, blocking, mutations) — constraints an agent cannot derive from the annotations or schema.

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

Conciseness5/5

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

Two sentences, zero filler, and the primary constraint (read-only, allowlisted) is front-loaded before the rejection list. Nothing could be cut without losing information.

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

Completeness3/5

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

There is no output schema, yet the description never explains what the command returns or how the allowlist is discovered, which matters for a tool that accepts arbitrary command names. Safety is well covered by annotations and the rejection list, but the 'what is actually allowed' gap is a meaningful omission for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (connection_id and response_format are undocumented), so the description must carry more weight. It clarifies that arguments are tokenized rather than a shell string, but that nuance is already present in the schema's own argument description, and it says nothing about connection_id or response_format.

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

Purpose4/5

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

States a specific verb+resource ('Run one ... read-only Redis command') with clear scope qualifiers: allowlisted, tokenized arguments. However, it does not distinguish itself from the sibling redis_execute, which is presumably the write-capable counterpart, so the agent must infer the boundary.

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 rejection list (KEYS, scripting, administration, pub/sub, transactions, blocking, mutations) implies when this tool is appropriate, and it is genuinely useful routing info. But it never names an alternative for the rejected categories (e.g. redis_execute) or states a positive condition for choosing this tool over redis_scan_keys.

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