Skip to main content
Glama

memxus

by com.memxus

List collections

list_collections
Read-onlyIdempotent

List memory collections (folders/scopes) for this user. GitHub/Notion syncs appear under project: when unified collections are enabled. Use before a scoped recall/get_context when the user mentions a project name, or to look up the team workspace names accepted by the workspace parameter of the other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of collections.
messageYesHuman-readable listing (same as content text).
collectionsYesCollection slugs and metadata.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, not destructive. Description adds useful context about sync naming conventions and preparatory use, without contradicting annotations.

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 with no wasted words. Purpose is front-loaded, and every sentence adds value.

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?

Given no parameters and an output schema exists, the description provides all necessary context: what the tool lists, naming nuances, and when to use it.

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?

No parameters are defined, so the schema coverage is 100% trivially. The description is not required to elaborate on parameters, and baseline 4 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 clearly states the tool lists memory collections for the user, with specific mention of GitHub/Notion syncs appearing under project:slug. This differentiates it from siblings like get_context and recall.

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 states when to use: before scoped recall/get_context when a project name is mentioned, or to look up workspace names for other tools. Provides clear context and alternatives.

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