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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Serverless Caches

aws_serverless_caches
Read-onlyIdempotent

Describes Amazon ElastiCache Serverless caches for Valkey, Redis OSS, and Memcached by AWS region, helping you inventory available serverless cache resources.

Instructions

DescribeServerlessCaches for ElastiCache Serverless (Valkey/Redis OSS/Memcached).

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

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond the annotations — nothing about pagination, filtering behavior, credential/region resolution, or scope of the returned inventory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words and the key qualifier (Serverless) placed early. The tradeoff is under-specification rather than verbosity: it is terse to the point of telling the agent little it could not read from the name.

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 the safety profile, so the description need not explain return values or read-only semantics. For a single-optional-parameter list tool, the definition is minimally adequate, but it leaves the serverless-vs-provisioned selection question entirely to inference.

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?

There is a single optional parameter with 100% schema description coverage ('AWS region; defaults to AWS_REGION'), so the schema fully documents it. The description adds no meaning about the region parameter or its fallback behavior, which is the correct baseline-3 case when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the operation (DescribeServerlessCaches) and scopes it to ElastiCache Serverless with the three supported engines, so the resource is identifiable. However, the phrasing largely restates the tool name in CamelCase rather than explaining in plain terms what an agent gets back, and it never contrasts with siblings like aws_cache_clusters (provisioned) or aws_serverless_snapshots.

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?

There is no when-to-use guidance, no exclusion conditions, and no named alternative. An agent must infer from the word 'Serverless' that this covers serverless caches rather than provisioned clusters, which is implied but never stated as a selection rule.

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