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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Cluster Triage

node_cluster_triage
Read-onlyIdempotent

Triages every shard primary in a cluster-mode group, ranking deduplicated node and pub/sub findings under one deadline; dead shards become critical findings without aborting.

Instructions

node_triage plus pub/sub pressure on every shard primary under one deadline: one ranked, deduplicated findings list naming node and shard (max 40). A dead shard is a critical finding, never fatal. Use first on a cluster-mode group.

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

Input Schema

NameRequiredDescriptionDefault
max_secondsNoTotal wall-clock budget, split across shards
max_workersNoConcurrent shard probes
per_node_timeoutNoExtra seconds to wait for a stuck shard

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: a single deadline budget, a 40-finding cap, and the rule that a dead shard is a critical finding rather than a fatal error. It does not say what happens when the deadline is exhausted mid-sweep.

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?

Three tight sentences with the composite purpose front-loaded, followed by output shape and then routing guidance. Slightly jargon-dense opening ('node_triage plus') assumes familiarity with the sibling, but nothing is wasted.

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?

Output schema exists, so return values need no explanation, and annotations cover safety. Given the tool's fan-out complexity, the description conveys enough to call it correctly, with only the deadline-exhaustion behavior and the definition of a 'cluster-mode group' left open.

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 100%, so max_seconds, max_workers, and per_node_timeout are already documented, including that the budget is split across shards. The phrase 'under one deadline' reinforces but does not add meaning beyond the schema; 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?

Names a specific composite operation: node_triage plus pub/sub pressure across every shard primary, producing one ranked deduplicated findings list. This distinguishes it from plain node_triage, though the relationship to other cluster siblings like node_cluster_health is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use first on a cluster-mode group' gives a clear entry-point recommendation, which is real when-to-use guidance. It stops short of stating when not to use it or which sibling supersedes it for non-cluster-mode single nodes.

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