Skip to main content
Glama
Filipe-Soares-de-Almeida

MemAI

by Filipe-Soares-de-Almeida
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_recent

Read-onlyIdempotent

List recent active memories in MemAI, optionally filtered by type or domain, to review what an AI agent remembers across sessions.

Instructions

List the most recent active memories, optionally filtered by type/domain.

Returns {"results": [...], "est_tokens": N}. Content is snippet-truncated per result -- call get_memory(uid) for the full record; a result's est_tokens estimates what that full record costs, and the top-level est_tokens is the sum over the results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoone memory type, as search() takes it; empty is every type.
limitNothe most results to return.
domainNocovers its subdomains, and a bare deep segment resolves to the branches holding it (see list_by_domain).
offsetNowhere the page starts; `next_offset`, when present, starts the next.
subtreeNoFalse narrows to the exact domain path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.16.1
    • addedInput schema / properties / domain / description
      Added value: +"covers its subdomains, and a bare deep segment resolves to the branches holding it (see list_by_domain)."
    • removedInput schema / properties / domain / title
      Removed value: -"Domain"
    • addedInput schema / properties / limit / description
      Added value: +"the most results to return."
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "where the page starts; `next_offset`, when present, starts the next.",
+  "type": "integer"
+}
    • addedInput schema / properties / subtree / description
      Added value: +"False narrows to the exact domain path."
    • removedInput schema / properties / subtree / title
      Removed value: -"Subtree"
    • addedInput schema / properties / type / description
      Added value: +"one memory type, as search() takes it; empty is every type."
    • removedInput schema / properties / type / title
      Removed value: -"Type"
    • removedInput schema / title
      Removed value: -"list_recentArguments"
  2. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / subtree
      Added value: +{
+  "default": true,
+  "title": "Subtree",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_recentOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so safety is covered. The description adds genuinely non-obvious behavior: results are snippet-truncated, per-result est_tokens estimates the cost of the full record, and the top-level est_tokens is the sum -- context the annotations and schema do not carry.

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?

The purpose is front-loaded in the first sentence, and the second sentence is dense but justified because it explains the return shape and token semantics that have no output schema to carry them. Slightly long but no empty sentences.

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?

With no output schema, the description usefully documents the return envelope and token-cost semantics, and it points to get_memory for full records. It is complete enough to call correctly, though it omits pagination behavior (next_offset) beyond what the schema hints at and does not clarify sibling selection.

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%, so the schema already explains type, limit, domain, offset, and subtree in detail. The description only adds 'optionally filtered by type/domain', which is weaker than the schema text itself, so it does not meaningfully enrich parameter meaning beyond the baseline.

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?

States a specific verb and resource ('List the most recent active memories') plus a scope qualifier (recent/active) and optional filters. It is clear what the tool returns, though it does not explicitly contrast itself with close siblings like search, recall, or timeline.

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

Usage Guidelines3/5

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

Provides one useful downstream pointer -- call get_memory(uid) for the full record because results are snippet-truncated -- which tells the agent how to follow up. However it gives no guidance on when to choose this over 'search', 'recall', 'timeline', or 'list_by_domain', so the core selection decision is left implicit.

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

Deploy Server

Other Tools