Skip to main content
Glama
Sign In
mcp-elasticache-ops

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Info

node_info
Read-onlyIdempotent

Returns raw Redis/Valkey INFO diagnostics for an ElastiCache node, optionally filtered to one section, with password-like keys masked.

Instructions

Raw INFO output, optionally for a single section. Password-like keys are masked.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoINFO section (server, memory, stats, replication, commandstats, keyspace...); omit for default

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false) and open-world access, so the bar is lower, yet the description adds real value beyond them: output is unprocessed raw INFO text, and password-like keys are masked. That masking note is a genuinely useful disclosure an agent cannot get from the annotations. It stops short of noting payload size or truncation for a full, unfiltered dump.

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?

Two short sentences with zero filler, and the core capability is front-loaded before the masking caveat. Nothing could be removed without losing information.

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?

This is a one-parameter read tool with an output schema, full schema coverage, and complete annotations, so the description needn't explain return values. It covers the essential caveats (raw format, masked secrets). The only omission is guidance on very large full-INFO responses, which is minor.

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% and the single optional parameter already enumerates example sections (server, memory, stats, replication, commandstats, keyspace) plus the null/omit default. The description's "optionally for a single section" and "omit for default" merely restate the schema, so baseline 3 applies with no extra semantics added.

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?

"Raw INFO output, optionally for a single section" states a specific verb+resource (return the node's INFO payload) and its scope. It is clear on its own, but gives no signal distinguishing it from section-specific siblings like node_memory, node_commandstats, or node_replication that presumably surface the same data in curated form.

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 word "raw" and the "omit for default" phrasing imply this is the unfiltered escape hatch when no curated sibling fits, but that is left to inference. There is no explicit statement of when to prefer this over node_memory or node_commandstats, and no when-not guidance.

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