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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Node Commandlog

node_commandlog
Read-onlyIdempotent

Inspect Valkey 8 command logs to find oversized slow, large-request, and large-reply payloads that SLOWLOG misses, with top commands by size and client address.

Instructions

Valkey 8 COMMANDLOG (slow, large-request, large-reply): oversized payloads SLOWLOG misses. Findings first, top commands by size and client addresses; no arguments or values. Other engines get a note.

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

Input Schema

NameRequiredDescriptionDefault
countNoEntries per type

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds real context beyond the read-only annotations: result ordering ("Findings first"), the shape of the summary (top commands by size and client addresses), a privacy guarantee ("no arguments or values"), and engine gating for non-Valkey targets. Rate limits and pagination behavior are not mentioned, but the annotations already carry the safety profile.

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 with the capability and the differentiator front-loaded; nothing is redundant. The telegraphic phrasing ("Other engines get a note") is slightly cryptic but costs no extra length.

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, return formatting need not be explained, and the description still covers engine applicability, privacy, and findings ordering. Missing only explicit guidance on how the three subtypes and 'count' interact (per-type versus total).

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% and the single parameter already documents default 10, max 128, and "Entries per type". The description's "top commands by size" loosely implies truncation/ordering but adds no syntax or semantics beyond the schema, so 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?

Names a specific resource (Valkey 8 COMMANDLOG) and enumerates its three subtypes (slow, large-request, large-reply), which lets an agent separate it from node_slowlog. The verb is only implied by the parenthetical rather than stated (e.g. 'fetch'/'list'), so it falls just short of a fully explicit 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 Guidelines4/5

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

"oversized payloads SLOWLOG misses" clearly positions it against the slowlog siblings, giving an implicit when-to-use rule. "Other engines get a note" also sets expectations outside Valkey 8, but there is no explicit exclusion or precedence statement against node_commandstats or node_latency.

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