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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Replication Group Audit

aws_replication_group_audit
Read-onlyIdempotent

Audits ElastiCache replication groups for HA and configuration risks, reporting issues like disabled Multi-AZ, missing replicas, encryption mix, and snapshot gaps with next-step tools.

Instructions

HA and config posture per replication group in one call. Findings first, each with a next tool: Multi-AZ or failover off, zero replicas, replicas in one AZ, big node without cluster mode, no snapshots or log delivery, encryption mix, network type.

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
replication_group_idNoAudit only this group (default: all groups)

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 declare read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description still adds real value by disclosing the output shape ('findings first') and that each finding carries a `next` tool, which tells the agent this is an actionable triage output rather than a raw data dump.

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 short sentences, front-loading the purpose and then the findings list. The trailing colon-separated enumeration is terse but readable and every item is a distinct check, so little is wasted.

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 no required parameters, rich annotations, and an output schema, the description needs only to convey purpose and output character, which it does. The only mild gap is the absence of any explicit comparison to the sibling listing/global-replication audit tools.

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%, with both parameters (region defaulting to AWS_REGION, and optional replication_group_id) fully documented in the schema. The description's 'per replication group' mirrors that scoping but adds no format or defaulting detail beyond what the schema already states, so the baseline applies.

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?

States a specific verb and scope: an audit of HA and config posture per replication group, and enumerates the exact finding classes it reports. That distinguishes it from a plain listing tool such as aws_replication_groups, though no sibling is named directly.

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?

Usage is implied by 'audit' and the enumerated findings, and 'in one call' hints that this is the consolidated option versus querying multiple tools. However, there is no explicit when-to-use or when-not-to-use statement, nor any named alternative for agents that only want a raw listing.

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