Skip to main content
Glama
Sign In
Redis MCP Server

Redis MCP Server

by Yuchenhui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hget

Retrieve the value of a specific field from a Redis hash. Provide the hash key and field name to get the corresponding value.

Instructions

Get the value of a field in a Redis hash.

Args: name: The Redis hash key. key: The field name inside the hash.

Returns: The field value or an error message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "key": "<key>"
    },
    "name": "hget"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
keyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A3.8/5.0
Behavior3/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 states 'Get the value' indicating a read operation and mentions returning the field value or error. This is basic but adequate for a simple read; no additional behavioral context (e.g., consistency, locking) is disclosed.

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 extremely concise: three lines covering purpose, parameters, and return. Every sentence adds value with no wasted words.

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 tool's simplicity (single field retrieval) and the presence of an output schema (as indicated by context signals), the description provides sufficient context. It mentions the return value and error case, making it complete for this straightforward 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?

Schema description coverage is 0%, so the description must compensate. It explains 'name: The Redis hash key. key: The field name inside the hash.', which adds meaning beyond the schema titles but lacks extra details like data type constraints or examples.

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 'Get the value of a field in a Redis hash.' It uses a specific verb and resource, distinguishing it from siblings like 'hgetall' (gets all fields) and 'get' (gets a string key).

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

Usage Guidelines3/5

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

The description implies usage for a single field but does not provide explicit guidance on when to use this tool versus alternatives like 'hgetall' or when not to use it. No exclusion criteria or context is given.

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