Skip to main content
Glama

memxus

by com.memxus

Get memory statistics

memory_stats
Read-onlyIdempotent

Show aggregate statistics about stored memories: the total count, a breakdown by memory_type and by collection, and storage bytes used versus the plan limit. Use to understand what is stored before browsing with list_memories, or to check remaining storage capacity. To show stats for a team workspace instead of personal memory, pass workspace: .

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoTo operate on a team workspace, pass its exact name, slug, or ID (e.g. "Acme"). Omit — or pass "personal" — for your personal memory (default). Every response echoes resolved_workspace so you can confirm where the operation actually happened. Call list_collections when unsure of the exact workspace name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of memories.
by_typeYesCount per memory_type.
messageYesHuman-readable statistics (same as content text).
by_collectionYesCount per collection slug.
resolved_workspaceNoThe workspace this call actually operated on (defense against writing to the wrong team by typo or name collision). id=null means Personal.
storage_bytes_usedNoTotal storage bytes used (content + metadata + embedding).
storage_bytes_limitNoPlan storage limit in bytes (-1 = unlimited).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true. The description adds useful context: the response echoes resolved_workspace and default behavior for workspace omission. 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?

Extremely concise: two sentences effectively convey purpose, usage, and parameter detail. Front-loaded with the main action.

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?

With one parameter, annotations, and output schema, the description covers all needed context: what stats are returned, when to use, and workspace handling. No gaps.

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% with detailed description. The tool description briefly repeats the parameter info but adds no new semantics beyond schema. 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?

The description explicitly states 'Show aggregate statistics about stored memories' with detailed breakdowns (count, memory_type, collection, storage bytes vs limit). It distinguishes from sibling tool list_memories by clarifying when to use each.

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?

Provides clear guidance: 'Use to understand what is stored before browsing with list_memories, or to check remaining storage capacity.' Also explains workspace parameter usage for team vs personal.

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

All memxus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: forget deletes, remember saves, update modifies, recall searches, list_memories lists, get_memory retrieves full details, get_context builds a context block, list_collections lists folders, memory_stats shows counts. There is no functional overlap that would confuse an agent.

Naming Consistency3/5

Names mix conventions: forget, recall, remember, update are single verbs; get_context, get_memory, list_collections, list_memories follow verb_noun; memory_stats is noun_noun. This inconsistency can make it harder for an agent to predict tool names.

Tool Count5/5

With 9 tools, the server is well-scoped for a memory management system. Each tool addresses a core operation (CRUD, search, stats, context building) without unnecessary redundancy. The count is appropriate for the domain.

Completeness4/5

The surface covers create (remember), read (list_memories, get_memory, recall, get_context), update (update), delete (forget), plus metadata tools (list_collections, memory_stats). Missing explicit filtering by tags or bulk operations, but these are minor gaps given the semantic search capability.

Resources