mcp-elasticache-ops

Overview Schema Source Related Servers Discussions Admin

Node Replication

node_replication

Read-onlyIdempotent

Inspect ElastiCache replication health by checking roles, replica byte lag, link status, backlog, and read-only or min-replica settings to flag down links and lagging replicas.

Instructions

Replication role, replicas with byte lag, link status, backlog, plus findings: links down, lagging replicas (also vs the primary offset on a replica), replica-read-only, min-replicas-to-write, cluster-allow-reads- when-down. Engine quirks are notes, not errors.

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

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

A3.8/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, it explains diagnostic behavior such as comparing lag against the primary offset when running on a replica. The statement that engine quirks are notes rather than errors is especially useful for interpreting severity, though freshness and finding thresholds remain unspecified.

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?

The description is compact, puts the reported replication data first, and ends with a useful interpretation caveat. Its noun-fragment opening and dense findings list slightly reduce scannability, but there is little filler.

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-argument, read-only diagnostic with an output schema, the description provides substantial scope and interpretation detail without needing to document a return structure. It could still clarify snapshot scope or freshness and how this tool should be selected relative to broader sibling diagnostics.

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 tool has no parameters, so there is no parameter meaning the description needs to supply and the baseline score of 4 applies. Its explanation of measurements and findings aids interpretation without needing to document invocation arguments.

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 conveys a replication status and diagnostic view through replication role, replica byte lag, link status, backlog, and specific findings. It lacks an explicit verb and does not directly distinguish itself from sibling health, info, or triage tools, so it does not reach a 5.

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 listed measurements and findings imply use when troubleshooting replication health, lag, broken links, and read/write safety configuration. However, there is no explicit when-to-use, when-not-to-use, prerequisite, or alternative-tool guidance.

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

Deploy Server