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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Parameters

aws_parameters
Read-onlyIdempotent

Describe an ElastiCache parameter group's cache parameters and flag risky settings like noeviction, small output buffers, timeout 0, or low maxmemory-samples to audit modified values.

Instructions

DescribeCacheParameters for a parameter group; by default only values changed (Source=user). Findings flag risky settings (noeviction, tiny output buffers, timeout 0, low maxmemory-samples).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parameter_group": "<parameter_group>"
    },
    "name": "aws_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoAWS region; defaults to AWS_REGION
only_modifiedNo
parameter_groupYes
diff_engine_defaultsNoCompare with DescribeEngineDefaultParameters and list only non-default values

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the default-filtering behavior and the fact that the output includes flagged risky settings (noeviction, small output buffers, timeout 0, low maxmemory-samples). That is real analytic context beyond the annotations.

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, zero filler: the operation and default scope come first, then the value-add (risk findings). Every clause carries information an agent can act on.

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?

An output schema and full annotations are present, so the description need not explain return shape; it covers the key default behavior. The remaining gap is the undocumented parameter_group identifier format and the precedence between only_modified and diff_engine_defaults.

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 50%: region and diff_engine_defaults are documented in the schema, while only_modified and parameter_group are not. The description rescues only_modified by explaining the Source=user default, but it never explains parameter_group format (name vs. identifier) or how diff_engine_defaults interacts with only_modified when both are set.

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?

Names the concrete operation (DescribeCacheParameters on a parameter group) and states the default scope explicitly ("by default only values changed (Source=user)"). That distinguishes it from aws_parameter_groups (listing groups) and aws_parameter_drift, though no sibling is named outright.

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 description implies when this is useful by describing the default filter and the risky-setting findings, but it never says when to prefer aws_parameter_drift or aws_parameter_groups instead, nor any prerequisites (e.g., the group must exist in the given region).

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