Skip to main content
Glama

list_rpush

Add elements to the end of a Redis list to manage data sequences or implement queue structures.

Instructions

右侧推入列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes列表键名
valuesYes要推入的值或值数组

Implementation Reference

  • The handler function that executes the list_rpush tool logic. It ensures Redis connection and calls rpush on RedisService with key and values, returning the result as text content.
    private async handleListRpush(args: any) {
      this.ensureRedisConnection();
      const result = await this.redisService!.rpush(args.key, args.values);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • The input schema definition for the list_rpush tool, specifying key (string) and values (string or array of strings).
    {
      name: 'list_rpush',
      description: '右侧推入列表',
      inputSchema: {
        type: 'object',
        properties: {
          key: { type: 'string', description: '列表键名' },
          values: {
            oneOf: [
              { type: 'string', description: '值' },
              { 
                type: 'array', 
                items: { type: 'string' },
                description: '值数组'
              }
            ],
            description: '要推入的值或值数组'
          }
        },
        required: ['key', 'values']
      }
  • The switch case in the CallToolRequestSchema handler that dispatches list_rpush calls to the handleListRpush method.
    case 'list_rpush':
      return await this.handleListRpush(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('right push list') but doesn't disclose behavioral traits such as whether it modifies data in-place, requires authentication, has rate limits, or what happens on errors (e.g., if the key doesn't exist). This is inadequate for a mutation tool with zero annotation coverage.

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?

Extremely concise with a single phrase '右侧推入列表', which is front-loaded and wastes no words. Every part earns its place by conveying the core action, though it lacks detail.

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 no annotations, no output schema, and a mutation tool (implied by 'push'), the description is incomplete. It doesn't cover behavioral aspects, return values, or error handling, making it insufficient for safe and effective use by an AI 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 100%, so the schema fully documents parameters (key and values). The description adds no meaning beyond the schema, as it doesn't explain parameter usage or constraints. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is provided.

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

Purpose3/5

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

The description '右侧推入列表' (right push list) indicates a Redis RPUSH operation but is vague. It specifies the verb 'push' and resource 'list' but lacks details on what 'right push' means operationally. It doesn't distinguish from siblings like list_lpush (left push), leaving ambiguity about directionality.

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 on when to use this tool versus alternatives. It doesn't mention sibling tools like list_lpush for left-side operations or list_rpop for popping, nor does it specify prerequisites like requiring a Redis connection (implied by context but not stated). Usage is implied by the name only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pickstar-2002/redis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server