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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Backup Audit

aws_backup_audit
Read-onlyIdempotent

Audit ElastiCache backup hygiene, flagging zero retention, missing recent automatic snapshots, failed latest snapshots, stale manual snapshots, and snapshots of deleted groups.

Instructions

Fleet backup hygiene (DescribeSnapshots plus groups/clusters). Findings first: retention 0, no recent automatic snapshot, latest failed, old manual snapshots, snapshots of deleted groups.

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
manual_daysNoFlag manual snapshots older than this (cost)
stale_hoursNoFlag when no automatic snapshot is newer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds that results are finding-oriented ('Findings first'), which tells the agent the response leads with problems rather than raw resources; it does not state API call volume, throttling risk, or whether multiple regions are scanned.

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 sentences, front-loaded with the resource and data sources, then the finding taxonomy. Slightly telegraphic fragments ('retention 0', 'latest failed') cost a little readability but each phrase carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety, so the description needn't explain returns. However, it never names the underlying service (the sibling set suggests ElastiCache clusters/replication groups) nor which resource types are audited, leaving scope ambiguous for a multi-region, four-check 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 description coverage is 100% with only three optional parameters, so baseline is 3. The description's mention of 'old manual snapshots' and 'no recent automatic snapshot' loosely maps to manual_days and stale_hours but adds no threshold semantics, units, or interaction guidance beyond the schema.

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+resource: a fleet backup hygiene audit combining DescribeSnapshots with groups/clusters, and enumerates the finding types (retention 0, no recent automatic snapshot, latest failed, old manual snapshots, snapshots of deleted groups). It does not name or distinguish itself from the close siblings aws_snapshots or aws_snapshot_restore_readiness, so an agent must infer the difference.

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 only implied: the enumerated hygiene checks make it reasonably clear this is the 'is my backup posture healthy' tool rather than a raw snapshot listing. There is no explicit when-to-use / when-not-to-use statement and no routing to aws_snapshots for plain listings, which is the main competing choice.

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