Skip to main content
Glama

Advanced: query XMemo memory stats

get_system_stats
Read-onlyIdempotent

Retrieve detailed memory statistics with filters for path, type, status, and time range, and group results by various dimensions for analysis.

Instructions

Detailed memory stats with filters and grouping. For a quick summary use memory_overview or memory_stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoOptional scope that narrows memory access; leave blank for the token default.
sinceNoOnly include memories or activity on or after this ISO 8601 timestamp.
top_nNoMaximum number of aggregate groups to return.
untilNoOnly include memories or activity on or before this ISO 8601 timestamp.
sourceNoOptional source filter for system statistics.
statusNoMemory status filter or update value, such as active, archived, deleted, or %.%
team_idNoOptional team/workspace identifier for team-scoped memory access.
group_byNoOptional grouping: none, month, agent, location, memory_type, type, source, path, bucket, day, or comma-separated advanced fields.
memory_typeNoMemory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.%
output_jsonNoReturn a machine-readable JSON response instead of a human-readable summary.
path_filterNoMemory path filter; % matches all paths.%

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so description only needs to add context. It adds that the tool is 'Advanced' and provides 'detailed stats'. No contradictions.

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: first states core purpose, second redirects to siblings. No wasted words, front-loaded with key 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?

Given the tool's complexity (11 parameters), high schema coverage, presence of output schema, and annotations, the description is sufficient. It covers the tool's role and differentiates from related tools. Minor lack: could mention read-only nature explicitly, but annotations cover that.

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%, so each parameter already has a description in the schema. The tool description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it provides 'detailed memory stats with filters and grouping' and explicitly distinguishes from siblings 'memory_overview' and 'memory_stats' as quick summaries.

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

Usage Guidelines5/5

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

Explicitly indicates when to use ('for detailed stats') and when not to ('for a quick summary use memory_overview or memory_stats'), providing clear context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server