Skip to main content
Glama
Sign In
Ragionex Memory MCP

Ragionex Memory MCP

Official
by ragionex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List memories (browse)

ragionex_list_memories
Read-onlyIdempotent

Browse Vault memories newest first when no topic is specified, filter by ISO 8601 creation dates, and page results with a cursor. Previews require full-record viewing before updates.

Instructions

Browse records in the selected Vault, most recently created first. Requires read permission. Use it when there is no topic, including requests to browse a date window. Optional start_date and end_date use ISO 8601 creation dates. limit is the page size, up to 100; pass next_cursor as cursor with the same filters for the next page. Listed content is a preview: read the full record and its revision with ragionex_view_memory before an update.

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": "ragionex_list_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records per page, most recent first. Default 50, maximum 100. Use next_cursor to continue with the same filters.
cursorNoThe next_cursor from the previous page. Omit or pass null for the first page; keep the same date filters when continuing.
end_dateNoOptional inclusive upper bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (end-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit or pass null for vague time.
start_dateNoOptional inclusive lower bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (start-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit or pass null for vague time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.7.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 128,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The next_cursor from the previous page. Omit or pass null for the first page; keep the same date filters when continuing."
+}
    • addedInput schema / properties / end_date / anyOf
      Added value: +[
+  {
+    "maxLength": 40,
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})?)?$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / end_date / description
      Previous value: -"Optional inclusive upper bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (end-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit for vague time."New value: +"Optional inclusive upper bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (end-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit or pass null for vague time."
    • removedInput schema / properties / end_date / maxLength
      Removed value: -40
    • removedInput schema / properties / end_date / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})?)?$"
    • removedInput schema / properties / end_date / type
      Removed value: -"string"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum memories to return, most recent first. Default 50. When the account holds more than this, the output says how many were omitted - narrow with project/date filters or raise the limit."New value: +"Maximum records per page, most recent first. Default 50, maximum 100. Use next_cursor to continue with the same filters."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +100
    • removedInput schema / properties / project
      Removed value: -{
-  "description": "Optional project filter. Omit to list memories across all projects.",
-  "maxLength": 50,
-  "minLength": 1,
-  "pattern": "^[a-z0-9-]{1,50}$",
-  "type": "string"
-}
    • addedInput schema / properties / start_date / anyOf
      Added value: +[
+  {
+    "maxLength": 40,
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})?)?$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / start_date / description
      Previous value: -"Optional inclusive lower bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (start-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit for vague time."New value: +"Optional inclusive lower bound for memory creation date. ISO 8601: 'YYYY-MM-DD' (start-of-day UTC) or 'YYYY-MM-DDTHH:MM:SSZ'. Set ONLY for exact, calendar-anchored time references; omit or pass null for vague time."
    • removedInput schema / properties / start_date / maxLength
      Removed value: -40
    • removedInput schema / properties / start_date / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})?)?$"
    • removedInput schema / properties / start_date / type
      Removed value: -"string"
  2. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: a 'Requires read permission' precondition, the newest-first ordering, and the pagination contract (pass next_cursor with the same filters). It stops short of describing result shape or error behavior, so not a 5.

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?

Four tight sentences, front-loaded with purpose and ordering before routing guidance. Minor redundancy with the schema on limit and ISO dates, but nothing that wastes the reader's attention.

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?

Covers purpose, permission, ordering, filtering, and pagination for a zero-required-parameter read tool with no output schema. The 'list is a preview, read the full record before an update' warning closes the main correctness risk. Only the concrete return shape is unspecified.

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 each parameter is already documented in detail, including ISO 8601 formats and the 100 max. The description restates 'start_date and end_date use ISO 8601 creation dates' and 'limit is the page size, up to 100', adding little beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Browse records in the selected Vault') plus the ordering guarantee ('most recently created first'). It is immediately distinguishable from topic-driven siblings like ragionex_recall_memory and single-record ragionex_view_memory.

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?

Explicit routing: 'Use it when there is no topic, including requests to browse a date window' tells the agent exactly when this tool wins over the recall path. It also names ragionex_view_memory as the required follow-up before an update, giving a concrete alternative and precondition.

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