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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Serverless Snapshots

aws_serverless_snapshots
Read-onlyIdempotent

Audits Amazon ElastiCache serverless cache snapshots to flag missing, failed, stale, expiring, or misconfigured backups, including missing KMS keys and unset retention.

Instructions

DescribeServerlessCacheSnapshots plus DescribeServerlessCaches: findings for caches without a recent snapshot, failed snapshots, snapshots about to expire, missing KMS key and unset retention.

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
stale_hoursNoFlag caches whose newest snapshot is older
snapshot_typeNoFilter by snapshot type
serverless_cache_nameNo

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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing exactly what the report flags, which tells the agent what diagnostic conclusions it can draw; it does not mention pagination, limits, or that the call spans multiple API operations in terms of cost.

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?

One dense sentence that front-loads the underlying API names followed by the finding list. There is no filler, though the API-name preamble is slightly less useful to an agent than the finding list that follows it.

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 four optional parameters, an output schema, and full annotation coverage, the definition supplies what an agent needs to decide and call it: the data sources and the exact checks performed. The only gap is the unspecified relationship to the sibling snapshot-audit tool.

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 coverage is 75%, so most parameters are already documented, which sets the baseline at 3. The description indirectly explains stale_hours via 'caches without a recent snapshot' and snapshot_type via 'snapshots about to expire', but adds no detail on region resolution or serverless_cache_name scoping.

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 the two underlying API operations (DescribeServerlessCacheSnapshots and DescribeServerlessCaches) and enumerates the findings produced, so the verb (audit/report) and resource (serverless cache snapshots) are unambiguous. It does not explicitly distinguish itself from the sibling aws_snapshots, which likely covers non-serverless snapshot auditing, leaving that boundary implicit.

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 enumerated finding categories (no recent snapshot, failed snapshots, expiring snapshots, missing KMS key, unset retention) imply when an agent would reach for this tool, but there is no explicit guidance on when to prefer it over aws_snapshots or aws_serverless_caches, nor any stated prerequisites.

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