Set a Redis string value with optional expiration. Requires disabling read-only mode.
设置字符串值（需要关闭只读模式）
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Redis键名 | |
| value | Yes | 要设置的值 | |
| ex | No | 过期时间（秒），不填则永不过期 |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description shoulders full responsibility. It only mentions a prerequisite but fails to disclose mutation effects (e.g., overwrites existing keys) or consequences of not following the condition.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the action, though it could usefully include more detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the description lacks crucial behavioral context for a mutating tool (e.g., idempotency, side effects), making it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the description adds no extra meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('设置字符串值' - set string value) and the resource, distinguishing it from sibling tools like get_key_value or delete_keys.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides a usage condition ('需要关闭只读模式' - requires turning off read-only mode), but does not explicitly exclude cases or mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.