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

mcp-elasticache-ops

by ritojoao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Memcached Stats

memcached_stats
Read-onlyIdempotent

Retrieves Memcached hit ratio, memory, evictions, and connection stats—or raw group output—to diagnose ElastiCache performance and capacity issues.

Instructions

Memcached summary (hit ratio, memory, evictions, connections) or a raw stats <group> output. Uses MEMCACHED_HOST/MEMCACHED_PORT.

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

Input Schema

NameRequiredDescriptionDefault
groupNostats group; empty for general

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add meaningful context beyond annotations by disclosing the connection configuration (MEMCACHED_HOST/MEMCACHED_PORT), but it says nothing about behavior when the host is unreachable or the group is unsupported.

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 short sentences, front-loaded with the summary contents and then the alternate mode; nothing is padded. The backticked `stats <group>` phrasing is slightly cryptic for an agent unfamiliar with the memcached protocol, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety, so the description needn't explain return values or reversibility. What remains missing is sibling differentiation and failure-mode context for a network-dependent stats call, which is a real gap given the 33-tool catalog around it.

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?

Schema coverage is 100% and the enum already documents each group value, so the baseline is 3. The description still earns a modest lift by explaining the output-shape consequence of the parameter — empty gives a curated summary, a named group gives raw `stats <group>` output — which the schema alone does not convey.

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 the resource (Memcached) and enumerates the concrete contents of the summary output (hit ratio, memory, evictions, connections), plus the alternate raw `stats <group>` mode. It is clear what the tool returns, but it never distinguishes itself from the sibling `memcached_cluster_stats`, which an agent could easily confuse with this one.

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: leaving `group` empty yields the summary while a non-empty group yields raw stats output. There is no explicit when-to-use statement, no guidance on when to prefer the cluster-level sibling, and no mention of prerequisites such as a reachable host.

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