XMemo

Show XMemo memory statistics

memory_stats

Read-onlyIdempotent

Shows aggregate statistics for all saved XMemo memories — counts by type, source, location, and optional time range when the user asks for counts, breakdowns, or distributions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No	Optional scope that narrows memory access; leave blank for the token default.
`since`	No	RFC 3339 timestamp with timezone offset (e.g., '2026-09-01T00:00:00+09:00'). Trigger: Call this whenever the user query mentions any relative or absolute time constraint in any language (e.g., today, yesterday, last week, last month, recently, Aug 1, Aug 10 to Sep 1, since Monday, before Sep 15, in Q3). Model responsibility: You (the calling LLM) know current date and user local time, so you must convert natural language time expressions into absolute timestamps. Consequence: If omitted, the server falls back to heuristic guessing which may misinterpret timezone day boundaries or relative dates.
`top_n`	No	Maximum number of aggregate groups to return.
`until`	No	RFC 3339 timestamp with timezone offset (e.g., '2026-09-02T00:00:00+09:00'). When used with since, defines the half-open interval [since, until) with until > since (maximum 90 days span). Trigger: Pass when the user query specifies an end date or bounded window in any language (e.g., yesterday end of day, by Aug 10, Aug 10 to Sep 1). Model responsibility: Convert natural language end bounds into absolute timestamps with timezone offsets. Consequence: If omitted, the window is open-ended on the upper side or derived heuristically.
`group_by`	No	Optional grouping: none, month, agent, location, memory_type, type, source, path, bucket, day, or comma-separated advanced fields.
`memory_type`	No	Memory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.	%
`output_json`	No	Return a machine-readable JSON response instead of a human-readable summary.
`path_filter`	No	Memory path filter; % matches all paths.	%

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 11, 2026
RemovedJul 31, 2026
First observedJun 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by clarifying that this is an aggregate/view operation over all saved memories, and it names the aggregation dimensions plus optional time-range filtering. It does not mention the heuristic fallback when since is omitted, but that nuance is captured in the parameter descriptions.

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?

The description is a single sentence that front-loads the primary outcome ('Shows aggregate statistics') and then packs the trigger condition and key dimensions into a compact subordinate clause. There is no filler, repetition of the schema, or unnecessary detail.

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

Completeness5/5

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

For a read-only statistics tool with 8 optional parameters, complete schema descriptions, a rich output schema, and safety annotations, the description covers the selection-level context and usage trigger. The remaining operational details are supplied by the schema, so nothing an agent needs to choose or invoke the tool correctly is missing.

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 description coverage is 100%, and the since/until parameters include exceptionally detailed trigger and model-responsibility guidance. The tool description itself only restates high-level grouping dimensions (type, source, location, time range) without adding parameter-level semantics, which matches the baseline score for high schema coverage.

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?

The description opens with a specific verb and resource: 'Shows aggregate statistics for all saved XMemo memories,' and lists concrete aggregation dimensions (type, source, location, time range). This makes it clearly distinguishable from sibling memory retrieval tools like recall_context or read_memory, which return actual memories rather than counts or breakdowns.

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?

The description explicitly states when the tool fits: 'when the user asks for counts, breakdowns, or distributions.' It does not name sibling alternatives or provide a when-not-to-use rule, so it stops short of fully explicit exclusion guidance, but the trigger condition is clear.

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

All XMemo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.