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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Triage

node_triage
Read-onlyIdempotent

Get an on-call health snapshot of the connected ElastiCache endpoint: memory, replication, clients, failed commands, slowlog, latency and DOCTOR findings ranked worst-first.

Instructions

On-call snapshot of the connected endpoint: health, memory, replication, clients, failed commandstats, top-5 slowlog, latency, DOCTOR. Findings worst-first (max 30); a failing section is reported unavailable. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/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 safety is covered. The description adds genuinely new behavioral facts: findings are ordered worst-first, capped at 30, and a failing section is degraded to 'unavailable' rather than aborting the call — that partial-failure semantics is the key thing an agent needs and cannot get from 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, both earning their place: the first front-loads the scope and enumerates the covered sections, the second covers ordering, the cap, and partial failure. 'Start here' is placed last as a call to action rather than buried.

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-value detail is correctly omitted, and with no parameters the input side needs nothing. What is slightly missing is cost/latency guidance — a full snapshot including DOCTOR and slowlog against a live endpoint is likely heavier than the single-topic siblings, and the description doesn't hint at that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The sentence about worst-first ordering and the 30-finding cap is closer to output behavior than parameter meaning, so no bonus is warranted.

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 states a concrete artifact — an on-call snapshot of the connected endpoint — and enumerates exactly which sections it aggregates (health, memory, replication, clients, failed commandstats, top-5 slowlog, latency, DOCTOR). That enumeration is what separates it from the single-topic siblings like node_memory or node_doctor, though no sibling is named explicitly; 'Start here' carries the differentiation implicitly.

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?

'Start here' plus the 'on-call snapshot' framing gives a clear entry-point directive, telling the agent to call this before drilling into focused tools. There is no explicit exclusion or 'use X instead when Y' statement, which keeps it short of a 5.

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