Synapse Layer — Trust Infrastructure for AI Agents

list_memories

Read-only

List memory metadata with pagination and governance limits.

Input Schema

Name	Required	Description
`limit`	No	Maximum memory metadata rows to return. Hard-capped: default 5, max 10. Values above 10 are silently reduced to 10.
`scope`	No	Explicit memory scope. "agent" (default, fail-closed) = lists memories for the given agent_id (or the token agent). "tenant" = lists memories across all agents of the authenticated tenant.
`subject`	No	ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email.
`agent_id`	No	Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred.
`project_id`	No	Optional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description	Default
`count`	Yes
`total`	No
`memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / project_id

Added value: +{
+  "description": "Optional project ID. Required for Corporate context unless the token is project-bound.",
+  "type": "string"
+}

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / subject

Added value: +{
+  "description": "ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email.",
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "limit_applied": {
-      "type": "number"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "createdAt": {
-            "description": "ISO-8601 timestamp.",
-            "type": "string"
-          },
-          "id": {
-            "type": "string"
-          },
-          "summary": {
-            "description": "Abstract summary — never plaintext content.",
-            "type": "string"
-          },
-          "tags": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "redacted": {
-      "type": "boolean"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "memories",
-    "count"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "limit_applied": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "createdAt": {
+            "description": "ISO-8601 timestamp.",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "description": "Abstract summary — never plaintext content.",
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "redacted": {
+      "type": "boolean"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

AddedApr 28, 2026
RemovedApr 27, 2026

Changed2 schema fields changedApr 24, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum memories to return (1–50, default: 20)."New value: +"Maximum memory metadata rows to return. Hard-capped: default 5, max 10. Values above 10 are silently reduced to 10."

changedInput schema / properties / scope / description

Previous value: -"Explicit memory scope. \"agent\" (default, fail-closed) = lists memories for the given agent_id (or the token agent). \"tenant\" = lists memories across all agents of the authenticated tenant. If omitted with agent_id present, \"agent\" is inferred; if both omitted, the token agent is used with a warning."New value: +"Explicit memory scope. \"agent\" (default, fail-closed) = lists memories for the given agent_id (or the token agent). \"tenant\" = lists memories across all agents of the authenticated tenant."

AddedApr 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the notion of governance limits but does not disclose anything concrete beyond that, leaving the hard-cap behavior to the schema rather than expanding on it.

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 description is a single front-loaded sentence with no waste. It is efficient but borderline terse, devoting no room to any usage or behavioral guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% schema coverage, the structured data carries most of the burden. The description is minimally adequate but thin given the tool has five parameters and numerous sibling alternatives it doesn't help the agent choose between.

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 every parameter is already fully documented (including the limit hard-cap and scope enum semantics). The description only gestures at "pagination and governance limits" without adding syntax or default detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ("List memory metadata") plus scoping (pagination and governance limits), so an agent knows this enumerates metadata rather than retrieving content. It does not, however, differentiate itself from siblings like recall, recall_memory, or search, leaving the metadata-vs-content distinction implicit.

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?

Usage is only implied: the word "metadata" hints this is for listing/enumeration rather than content retrieval, and "governance limits" suggests constrained listing. There is no explicit when-to-use, when-not-to-use, or named alternative among the many recall/search siblings.

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

All Synapse Layer — Trust Infrastructure for AI Agents tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

list_memories

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources