Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
connect_redisC

连接到 Redis 服务器

disconnect_redisB

断开与 Redis 服务器的连接

string_setC

设置字符串键值

string_getC

获取字符串值

string_incrC

递增数值

string_decrC

递减数值

string_msetC

批量设置键值

string_mgetC

批量获取键值

hash_setC

设置哈希字段

hash_msetC

批量设置哈希字段

hash_getC

获取哈希字段

hash_getallC

获取所有哈希字段

hash_delC

删除哈希字段

list_lpushC

左侧推入列表

list_rpushC

右侧推入列表

list_lpopC

左侧弹出列表

list_rpopC

右侧弹出列表

list_rangeD

获取列表范围

set_addC

添加集合成员

set_removeC

移除集合成员

set_membersC

获取集合所有成员

zset_addC

添加有序集合成员

zset_removeC

移除有序集合成员

zset_rangeC

获取有序集合范围

key_deleteC

删除键

key_expireC

设置键过期时间

key_ttlC

获取键过期时间

key_searchC

查找匹配的键

key_typeC

获取键类型

key_infoC

获取键信息

key_delete_patternC

批量删除匹配的键

db_flushB

清空当前数据库

backup_createC

创建 Redis 数据备份

backup_restoreC

从备份恢复 Redis 数据

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 34 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity, as they are organized by Redis data types (hash, list, set, string, zset) and operations (get, set, delete, etc.), plus connection and backup utilities. The naming explicitly indicates the target resource and action, making misselection unlikely.

Naming Consistency5/5

The tool names follow a highly consistent verb_noun pattern throughout, such as hash_get, list_lpush, string_set, and backup_create. All tools use snake_case with no deviations, making the naming predictable and easy to understand.

Tool Count3/5

With 34 tools, the count is borderline high for a Redis server, as it includes comprehensive coverage of data types and operations but may feel heavy compared to typical MCP servers (usually 3-15 tools). However, it is reasonable given Redis's feature-rich nature.

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for Redis operations, including connection management, data manipulation for all major types (hash, list, set, string, zset), key operations, and backup/restore. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues