Skip to main content
Glama

memory_stats

Retrieve memory store statistics, cross-agent sources, weights, and dependency status to verify what a shared SQLite memory file holds and how it is attributed.

Instructions

Return memory store statistics, cross-agent sources, weights, and dependency status.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The verb "Return" implies a non-mutating read, which is useful, but there is no explicit statement of side-effect freedom, permission or auth requirements, cost, or whether the statistics are live versus cached.

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?

A single front-loaded sentence with no filler, and the core purpose leads. Minor vagueness in terms like "weights" and "dependency status" leaves the reader guessing slightly, 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?

The tool is simple: no parameters and a declared output schema, so return values need not be explained in prose. The description says enough to select the tool correctly, with the only real gap being the absence of explicit usage context.

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; baseline applies. It does not need to explain argument syntax or defaults.

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?

"Return memory store statistics" names a specific verb and resource, and the enumerated contents (cross-agent sources, weights, dependency status) make the scope concrete. It is clearly distinguishable from the fact/episode retrieval siblings, though it does not explicitly name or contrast any of them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no pointer to alternatives such as search_facts or list_facts. An agent must infer that this is a diagnostic/inspection call rather than a data-retrieval call.

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