Skip to main content
Glama
redis

Redis MCP Server

Official
by redis

get

Retrieve stored string values from Redis by specifying their keys to access data in agentic applications.

Instructions

Get a Redis string value.

Args: key (str): The key to retrieve.

Returns: str, bytes: The stored value or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the MCP 'get' tool, which retrieves a string value from Redis using the r.get(key) command, handles bytes decoding, and returns errors appropriately.
    @mcp.tool()
    async def get(key: str) -> Union[str, bytes]:
        """Get a Redis string value.
    
        Args:
            key (str): The key to retrieve.
    
        Returns:
            str, bytes: The stored value or an error message.
        """
        try:
            r: Redis = RedisConnectionManager.get_connection()
            value = r.get(key)
    
            if value is None:
                return f"Key {key} does not exist"
    
            if isinstance(value, bytes):
                try:
                    text = value.decode("utf-8")
                    return text
                except UnicodeDecodeError:
                    return value
    
            return value
        except RedisError as e:
            return f"Error retrieving key {key}: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions retrieving a value or an error message, which hints at read-only behavior, but lacks details on permissions, rate limits, error conditions (e.g., key not found), or whether it's destructive. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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?

The description is appropriately sized and front-loaded, with the core purpose stated first ('Get a Redis string value'), followed by structured sections for Args and Returns. Every sentence earns its place, making it efficient and easy to parse without unnecessary verbosity.

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?

Given the tool's low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is somewhat complete but has gaps. It covers the basic purpose and parameter semantics but lacks usage guidelines and sufficient behavioral transparency, making it adequate but with clear room for improvement in context.

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

Parameters4/5

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

The description adds meaningful context beyond the input schema. The schema has 0% description coverage and only lists 'key' as a string parameter, but the description clarifies that 'key' is for retrieving a Redis string value, providing essential semantic information that compensates for the low schema coverage.

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?

The description clearly states the verb ('Get') and resource ('a Redis string value'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'hget' (hash get) or 'json_get', which also retrieve values but from different Redis data structures, leaving some ambiguity about when this tool specifically applies versus those alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'hget', 'json_get', and 'scan_keys' that also retrieve data, there's no indication that this is specifically for string values or any context about prerequisites or exclusions, leaving usage unclear.

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/redis/mcp-redis'

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