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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aws Users

aws_users
Read-onlyIdempotent

Lists ElastiCache Redis/Valkey users with RBAC authentication and access strings, excluding passwords, to flag overbroad access and passwordless accounts.

Instructions

DescribeUsers (RBAC): authentication type and access strings, never passwords. Flags users with '~* +@all' access and users without a password.

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

Input Schema

NameRequiredDescriptionDefault
engineNoEngine filter
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds meaningful behavior: passwords are never returned (a security-relevant guarantee about output), and the result set explicitly flags users with '~* +@all' access and users lacking a password. That goes beyond what the annotations convey.

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 compact sentences with the core guarantee ('never passwords') and the flagging behavior front-loaded; nothing is wasted. The parenthetical '(RBAC)' is slightly cryptic but does not cost much.

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 exists, so return structure need not be explained, and both optional parameters are fully described in the schema. The description covers what the tool does and the notable result semantics; only usage routing against sibling audit tools is absent.

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% and both parameters (engine, region) are documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about filtering behavior, engine semantics, or how region defaulting interacts with results.

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 underlying operation (DescribeUsers) and the domain (RBAC), and specifies what is returned: authentication type and access strings. It clearly distinguishes the resource from sibling audit tools like aws_security_audit or aws_parameters, though 'DescribeUsers' is an API-style name rather than a plain verb+resource statement.

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 mention of flagging risky access patterns signals an audit/inspection use case, but there is no explicit statement of when to choose this tool, prerequisites, or exclusions relative to other aws_* audit tools. An agent can infer intent but gets no routing guidance.

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