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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Cache Clusters

aws_cache_clusters
Read-onlyIdempotent

Retrieve ElastiCache cache cluster details including engine version, node type, parameter group status, maintenance windows, pending changes, and node endpoints for diagnosing cluster configuration.

Instructions

DescribeCacheClusters: per-node-cluster engine version, node type, parameter group and apply status, maintenance window, pending changes and node endpoints.

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
show_nodesNo
cache_cluster_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and open-world. The description adds useful context by enumerating the cluster attributes returned, including pending changes and node endpoints, but it does not explain filtering behavior or what happens when cache_cluster_id is omitted.

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?

The description is a single compact sentence with no filler, front-loading the operation name and then listing the relevant returned attributes. It is terse but appropriately sized for a read-only describe tool.

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?

The tool has annotations and an output schema, so the description does not need to carry the full burden alone. However, it omits important calling details such as whether omitting cache_cluster_id returns all clusters and how show_nodes changes the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description does not clarify the meaning or effect of show_nodes or cache_cluster_id. It leaves key parameter behavior undocumented in both the schema and the description.

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 DescribeCacheClusters operation and enumerates specific returned attributes such as engine version, node type, maintenance window, pending changes, and node endpoints. This makes the resource and output scope clear, though it does not explicitly distinguish itself from siblings like aws_serverless_caches or aws_cluster_overview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it state any exclusions or prerequisites. An agent can infer that it retrieves cache cluster details, but the usage context is not spelled out.

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