Skip to main content
Glama

memory_stats

Read-only

Retrieve global MCP server cache statistics to monitor performance, inspect hit rates and cache sizes, and debug caching issues across tool calls.

Instructions

Get MCP server global cache statistics for performance monitoring.

                Returns detailed metrics about storage and memory service caching,
                including hit rates, initialization times, and cache sizes.

                This tool is useful for:
                - Monitoring cache effectiveness
                - Debugging performance issues
                - Verifying cache persistence across MCP tool calls

                Returns cache statistics including total calls, hit rate percentage,
                storage/service cache metrics, performance metrics, and backend info.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating operation, so the description does not need to repeat that. It adds value by naming what is measured (hit rates, initialization times, cache sizes, backend info) and by identifying the scope as global/server-wide rather than per-memory, which is the key behavioral fact an agent needs. It omits whether the call is expensive or paginated, but for a zero-parameter stats read that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent is front-loaded, but the return contents are announced three separate times ('Returns detailed metrics...', 'Returns cache statistics including...'), plus a redundant bulleted use-case block. Trimming the duplicated return sentences would lose no information.

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?

Because there is no output schema, the description carries the burden of explaining what comes back, and it does list the metric families (hit rate, storage/service cache metrics, performance metrics, backend info). The enumeration is vague about exact field names and shapes, but it is sufficient for an agent to decide whether to call the tool and how to interpret the result.

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 no parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool 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 opens with a specific verb and resource: 'Get MCP server global cache statistics for performance monitoring,' which tells an agent exactly what the tool returns. It does not, however, distinguish this tool from near-siblings such as memory_health or memory_quality, so the agent must infer the boundary itself.

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?

It gives three concrete use cases: monitoring cache effectiveness, debugging performance issues, and verifying cache persistence across tool calls. This context is clear but there are no exclusions and no mention of when a different sibling tool would be preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.