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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Cluster Health

node_cluster_health
Read-onlyIdempotent

Probes every cluster node with bounded concurrency and per-node timeouts, then flags memory or ops skew, failed nodes, uncovered slots, and replica lag for ElastiCache health checks.

Instructions

Cluster-mode fan-out: INFO on every node (bounded concurrency, per-node timeout) flagging memory/ops skew across shards, failed nodes, uncovered slots and replica lag.

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

Input Schema

NameRequiredDescriptionDefault
max_workersNoConcurrent node probes
per_node_timeoutNoSeconds to wait 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 cover readOnly, idempotent, and openWorld, so the bar is lower, and the description adds real context on top: bounded concurrency, per-node timeouts, and the actual diagnostic conditions it reports (skew, failed nodes, uncovered slots, replica lag). It stops short of saying how partial failures are surfaced or whether slow nodes truncate the result.

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?

A single dense sentence with the scope front-loaded ('Cluster-mode fan-out') followed by mechanics and then the observed signals. Every clause contributes, though the compressed telegraphic style and lack of sentence breaks makes it slightly harder to parse than a clean two-sentence split.

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?

With an output schema present, the description needn't explain return values, and both parameters are fully covered by the schema, so what remains is behavioral scope — which it handles well. The only real omission is comparative guidance against the many node_cluster_* siblings, which is a guidance issue rather than a completeness gap for calling the tool correctly.

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% with only two parameters, both documented with defaults, ranges, and units in the schema. The description's mention of 'bounded concurrency' and 'per-node timeout' merely echoes those parameters without adding syntax, tuning advice, or failure semantics, so the baseline of 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 gives a specific verb and resource — 'Cluster-mode fan-out: INFO on every node' — plus the exact signals it flags (memory/ops skew across shards, failed nodes, uncovered slots, replica lag). That phrasing implicitly separates it from the single-node 'node_health' sibling, but no sibling is ever named, so the differentiation is inferential rather than explicit.

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 through 'Cluster-mode fan-out' and 'every node', which signals cluster-wide scope rather than a single node. There is no explicit statement of when to prefer this over node_health or node_cluster_triage, and no guidance on cost or when fan-out is overkill; the agent must infer the context.

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