Skip to main content
Glama
redis

Redis MCP Server

Official
by redis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set

Store a string value in Redis under a specified key, with an optional expiration time for automatic removal.

Instructions

Set a Redis string value with an optional expiration time.

Args: key (str): The key to set. value (str, bytes, int, float, dict): The value to store. expiration (int, optional): Expiration time in seconds.

Returns: str: Confirmation message or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
valueYes
expirationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • addedInput schema / properties / expiration / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / expiration / type
      Removed value: -"integer"
    • changedInput schema / properties / value / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "format": "binary",
-    "type": "string"
-  },
-  {
-    "type": "integer"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "format": "binary",
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "setOutput",
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description provides some behavioral context (optional expiration, return type), but it omits important traits such as overwrite behavior on existing keys, size limits, or automatic serialization of dict values to JSON.

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 concise and front-loaded, with a clear one-sentence purpose followed by parameter details. It is appropriately sized for a simple tool, though it could be slightly more concise by omitting the 'Args:' formatting.

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

Completeness4/5

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

Given the simplicity of the tool (3 parameters, no annotations, output schema present), the description covers the essential behavior and parameters. It lacks some edge-case details but is generally sufficient for a basic Redis SET operation.

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?

The description clarifies that value can be 'str, bytes, int, float, dict' and that expiration is optional, adding meaning beyond the raw schema types. However, it does not explain the serialization of dicts or the exact behavior of expiration (e.g., units).

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 verb 'Set' and the resource 'a Redis string value', which distinguishes it from sibling tools like 'get', 'delete', or 'hset'. The addition of 'with an optional expiration time' further clarifies the scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'hset' or 'json_set'. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage without additional support.

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