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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Snapshot Restore Readiness

aws_snapshot_restore_readiness
Read-onlyIdempotent

Checks restore readiness for one ElastiCache replication group or serverless cache by flagging backup, snapshot, KMS, size, and engine-upgrade blockers.

Instructions

Can this group or serverless cache be restored? Pass exactly one id. Findings first: backups off, stale, expired or failed snapshot, none before an engine upgrade, KMS mismatch, snapshot too big for the target node.

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
stale_hoursNoFlag when no automatic snapshot is newer
replication_group_idNoReplication group to check
serverless_cache_nameNoServerless cache to check instead

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value on top: it enumerates the concrete failure classes surfaced (backups off, stale, expired, failed, no snapshot before engine upgrade, KMS mismatch, snapshot too large for target node) and states that findings are returned first, which shapes how the agent should read the response.

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 sentences, front-loaded with the core question, then the calling constraint, then the finding taxonomy. No filler and nothing buried.

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 an output schema present, return values need no explanation, and the schema covers region and stale_hours defaults. The description supplies the diagnostics taxonomy and the single-id rule, leaving only minor gaps such as how findings are ranked or whether remediation hints are included.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above baseline by stating an exclusivity constraint between the two identifier parameters ('exactly one id') that the schema does not encode via anyOf or oneOf. It also implicitly ties stale_hours to the 'stale' finding category.

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 opening question, 'Can this group or serverless cache be restored?', names the exact resource types and the decision being made, which separates it from inventory-style siblings like aws_snapshots or aws_replication_groups. It stops short of naming any sibling explicitly, so an agent must infer the boundary itself.

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?

'Pass exactly one id' tells the agent how to call it, and the question framing implies a pre-restore readiness check. There is no explicit statement of when to prefer this over aws_snapshots or aws_backup_audit, 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