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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Hot Slots

node_hot_slots
Read-onlyIdempotent

Detect shard skew and hot slots in ElastiCache cluster-mode by sampling slots and reporting per-shard keys, memory, ops/sec, and hot shard/slot findings.

Instructions

Cluster-mode shard skew and hot slots: per-shard keys, memory, ops/sec plus CLUSTER COUNTKEYSINSLOT on a capped slot sample. Findings name hot shards and slots; reached N/M shards. Counts only.

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": "node_hot_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_secondsNoTotal budget
max_workersNoConcurrent probes
slots_per_shardNoSlots sampled per shard
per_node_timeoutNoSeconds per node

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, openWorld, so the safety profile is covered. The description adds genuinely new behavior: the slot sample is capped (results are sampled, not exhaustive), partial reach is reported via `reached N/M shards`, and output is "Counts only" with no key names or values — all things the annotations do not 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 dense sentences, front-loaded with the resource and measurements, followed by output-shape notes. No filler, though the backticked `reached N/M shards` fragment is slightly cryptic without surrounding context.

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 detail is not the description's burden; it still usefully flags sampling and partial shard coverage so the agent won't misread incomplete results as full-cluster truth. Missing only the cluster-mode-only caveat stated plainly and any sibling routing.

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%, so all four parameters (budget, workers, slots_per_shard, per-node timeout) are already self-documenting. The description only loosely gestures at sampling via "capped slot sample," adding no syntax, interaction, or tuning guidance beyond the schema — the baseline 3 applies.

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 a specific diagnostic: cluster-mode shard skew and hot slots, enumerating the exact measurements (per-shard keys, memory, ops/sec) and the underlying command (CLUSTER COUNTKEYSINSLOT). It is clearly distinguishable from sibling keyspace/health tools, though it never explicitly names an alternative to route against.

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?

"Cluster-mode" implies the precondition (non-cluster deployments won't yield meaningful output), and "capped slot sample" implies approximate results. But there is no explicit when-to-use vs. when-not, and no pointer to node_cluster_keyspace_sample or node_keyspace_sample as the non-cluster or full-keyspace alternatives.

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