Skip to main content
Glama
Sign In
marsnme

marsnme

by Marsmanleo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_memories

Review recent short-term memories in reverse chronological order. Use this daily log to check duplicates or browse captured activity.

Instructions

List recent short-term memories from demo.memories in reverse chronological order — like a daily log or activity feed. Use this to review what was recently captured, check for duplicate memories before inserting, or browse recent activity. This is a time-ordered listing tool, not a search tool. For semantic search by meaning, use search_memories instead. For long-term knowledge retrieval, use recall. Returns memory body, source, creation time, and expiration status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of memories to return (default 20)
sourceNo
unexpired_onlyNoWhen true (default), only return memories that have not yet expired. Set false to include expired entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "perplexity",
-  "cursor",
-  "warp",
-  "openclaw",
-  "hermes"
-]New value: +[
+  "perplexity",
+  "cursor",
+  "warp",
+  "openclaw",
+  "hermes",
+  "draft",
+  "grok"
+]
  2. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of memories to return (default 20)"
    • addedInput schema / properties / unexpired_only / description
      Added value: +"When true (default), only return memories that have not yet expired. Set false to include expired entries."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns memory body, source, creation time, and expiration status, and that it orders reverse chronologically with an option to filter unexpired memories. While it doesn't mention mutability or idempotency, listing tools are inherently read-only; still, the description adds useful behavioral context beyond the schema.

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 four sentences, each with a clear purpose: first defines the tool, second gives use cases, third distinguishes from alternatives, fourth lists return fields. 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 no output schema, the description helpfully lists return fields. It explains ordering and filtering. However, it doesn't describe pagination or the exact behavior of 'limit' (e.g., max items), nor how 'source' filter interacts with the data. Still, it's fairly complete for a simple listing tool.

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 67% (limit and unexpired_only have descriptions). The tool description doesn't add extra meaning for parameters beyond what's in the schema, except it mentions 'expiration status' which relates to unexpired_only. It doesn't clarify how 'source' filter works but the enum values are self-explanatory. Adequate but doesn't significantly improve on the schema.

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 recent short-term memories in reverse chronological order, likening it to a daily log or activity feed. It distinguishes from siblings by specifying it's a time-ordered listing tool, not a semantic search tool (search_memories) or long-term retrieval (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: to review recent captures, check for duplicates before inserting, or browse recent activity. Also explicitly says when not to use and provides alternatives: 'not a search tool' – use search_memories for semantic search, use recall for long-term knowledge retrieval.

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