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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Cluster Overview

aws_cluster_overview
Read-onlyIdempotent

Summarizes replication group health via shards, replicas, AZ spread, failover, engine version, and node CloudWatch signals; flags outliers, reader gaps, and right-sizing. Omit group ID for fleet scan.

Instructions

One findings-first call per replication group: shards, replicas, AZ spread, failover, engine version plus per-node CloudWatch signals; flags outlier nodes, reader gaps, right-sizing. No group id: fleet mode.

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": "aws_cluster_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
minutesNoCloudWatch window (multiple of 5 min is fine)
replication_group_idNoReplicationGroupId to summarise; omit for a fleet pass over every configured region

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world, so the added value here is the disclosure that this performs analysis and emits findings/flags rather than raw data, and that omitting the group id fans out across every configured region — a meaningfully heavier operation. It does not warn about cost, latency, or throttling of that fleet pass, which keeps it from a 5.

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 tight sentences with the scope statement front-loaded ('One findings-first call per replication group') and the mode switch at the end. The compressed noun list and 'findings-first' jargon are dense but every clause carries information; nothing is redundant.

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?

With a 100%-documented schema, full annotations, and an output schema, the description only needs to establish scope and the per-group vs fleet distinction, and it does both. The only gap is the absence of any caution about the breadth/latency of a fleet-wide scan, which a zero-required-parameter tool would benefit from stating.

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%, so all three parameters are already documented, including that omitting replication_group_id yields a fleet pass. The description's 'No group id: fleet mode' largely restates the schema rather than adding new semantics, and it says nothing about the region default or the CloudWatch window meaning beyond what the schema states.

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 names a concrete resource (replication groups) and enumerates the payload it returns: shards, replicas, AZ spread, failover, engine version, and per-node CloudWatch signals, plus the findings it produces (outlier nodes, reader gaps, right-sizing). The phrase 'No group id: fleet mode' also separates the fleet-wide behaviour from per-group calls. It does not name which sibling tool to use for a narrower scope, so it stops short of 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 closing clause gives one invocation rule (omit the id to scan the whole fleet), which is real but minimal guidance. There is no statement of when to prefer this over the narrower audit, metrics, or readiness siblings, and no prerequisites or exclusion conditions are 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