mcp-elasticache-ops

Overview Schema Source Related Servers Discussions Admin

Node Config

node_config

Read-onlyIdempotent

Inspect allowlisted Redis/Valkey CONFIG settings like maxmemory policy, timeouts, appendonly, buffer limits, notifications, and slowlog thresholds; fall back to AWS parameters when CONFIG is refused.

Instructions

Allowlisted CONFIG GET view (maxmemory policy, timeout, appendonly, output buffer limits, keyspace notifications, slowlog/latency thresholds, io-threads) with findings. Points at aws_parameters when CONFIG is refused, as ElastiCache usually does.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "node_config"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent read, so the description's job is added context — and it delivers the key operational fact that only an allowlisted subset of directives is returned and that CONFIG may be refused entirely. That refusal behavior is exactly the kind of thing an agent cannot infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and resource, then the fallback caveat. The long parenthetical directive list is informative but dense; trimming to the most decision-relevant directives would tighten it without losing much.

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?

For a zero-param tool with an output schema, return-value detail is unnecessary, and the description covers scope and the failure/fallback path. It stops short of noting whether findings are always attached or what the refusal error looks like, but that is a minor residual.

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?

Zero parameters, so there is no parameter meaning to convey; baseline 4 applies. The description correctly spends no words on inputs and instead explains output scope.

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?

States a concrete verb and resource ('CONFIG GET view') plus the exact scope of the allowlisted subset enumerated in the parenthetical, so the agent knows precisely what comes back. It also names the sibling (aws_parameters) it hands off to, which separates it from the broader node_memory/node_info family.

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

Usage Guidelines4/5

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

Gives an explicit conditional route: when CONFIG is refused (typical on ElastiCache), use aws_parameters. It doesn't state a positive 'use this when...' trigger for the tool itself, but the scope list makes the intended use clear enough to act on.

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

Deploy Server