Synapse Layer — Trust Infrastructure for AI Agents

recall

Read-only

Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Recall routing mode. "temporal" = pure chronological, "semantic" = FTS + TQ ranking, "priority" = critical/high-TQ first, "hybrid" = weighted blend, "auto" = detect from query (default).
`limit`	No	Maximum memories to return (1–50, default: 10).
`query`	Yes	What to recall — natural language query for memory retrieval.
`scope`	No	Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, "agent" is inferred; if both omitted, the token agent is used (verified-token scope).
`reason`	Yes	REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: "User asked me to summarize last week decisions."
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`scope`	Yes
`memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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": {
+        "properties": {
+          "content": {
+            "type": "string"
+          },
+          "createdAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "similarity": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "memories",
+    "count",
+    "scope"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "fallback": {
-      "type": "boolean"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "agent": {
-            "type": "string"
-          },
-          "confidence": {
-            "enum": [
-              "high",
-              "medium_fts",
-              "low"
-            ],
-            "type": "string"
-          },
-          "content": {
-            "description": "Memory content (truncated to 300 chars in recall).",
-            "type": "string"
-          },
-          "hybridScore": {
-            "type": "number"
-          },
-          "id": {
-            "type": "string"
-          },
-          "intent": {
-            "type": "string"
-          },
-          "is_critical": {
-            "type": "boolean"
-          },
-          "memory_type": {
-            "type": "string"
-          },
-          "timestamp": {
-            "description": "ISO-8601 timestamp.",
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "query": {
-      "type": "string"
-    },
-    "queryCacheHit": {
-      "type": "boolean"
-    },
-    "recallLatencyMs": {
-      "type": "number"
-    },
-    "recall_mode": {
-      "type": "string"
-    },
-    "redacted": {
-      "type": "boolean"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    },
-    "sessionCacheHit": {
-      "type": "boolean"
-    }
-  },
-  "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"
+    },
+    "fallback": {
+      "type": "boolean"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent": {
+            "type": "string"
+          },
+          "confidence": {
+            "enum": [
+              "high",
+              "medium_fts",
+              "low"
+            ],
+            "type": "string"
+          },
+          "content": {
+            "description": "Memory content (truncated to 300 chars in recall).",
+            "type": "string"
+          },
+          "hybridScore": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "intent": {
+            "type": "string"
+          },
+          "is_critical": {
+            "type": "boolean"
+          },
+          "memory_type": {
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "ISO-8601 timestamp.",
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "queryCacheHit": {
+      "type": "boolean"
+    },
+    "recallLatencyMs": {
+      "type": "number"
+    },
+    "recall_mode": {
+      "type": "string"
+    },
+    "redacted": {
+      "type": "boolean"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    },
+    "sessionCacheHit": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedApr 29, 2026

changedInput schema / properties / reason / description

Previous value: -"REQUIRED (MEMORY_EXPORT_GOVERNANCE_V1): human-readable justification for retrieving PLAINTEXT memory content. Must be 10–200 characters. Logged in the anti-dump audit trail. Example: \"User asked me to summarize last week's migration decisions.\""New value: +"REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: \"User asked me to summarize last week decisions.\""

changedInput schema / properties / scope / description

Previous value: -"Explicit memory scope. \"agent\" (default, fail-closed) = limits recall to the given agent_id (or the token agent). \"tenant\" = cross-agent recall within 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) = limits recall to the given agent_id (or the token agent). \"tenant\" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, \"agent\" is inferred; if both omitted, the token agent is used (verified-token scope)."

Changed4 schema fields changedApr 28, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Agent identifier to scope memory recall. Defaults to \"default\"."New value: +"Agent identifier (canonical or alias). Used only when scope=\"agent\" or scope is inferred."

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED (MEMORY_EXPORT_GOVERNANCE_V1): human-readable justification for retrieving PLAINTEXT memory content. Must be 10–200 characters. Logged in the anti-dump audit trail. Example: \"User asked me to summarize last week's migration decisions.\"",
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "description": "Explicit memory scope. \"agent\" (default, fail-closed) = limits recall to the given agent_id (or the token agent). \"tenant\" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, \"agent\" is inferred; if both omitted, the token agent is used with a warning.",
+  "enum": [
+    "agent",
+    "tenant"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "reason"
+]

Changed4 schema fields changedApr 27, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Agent identifier (canonical or alias). Used only when scope=\"agent\" or scope is inferred."New value: +"Agent identifier to scope memory recall. Defaults to \"default\"."

removedInput schema / properties / reason

Removed value: -{
-  "description": "REQUIRED (MEMORY_EXPORT_GOVERNANCE_V1): human-readable justification for retrieving PLAINTEXT memory content. Must be 10–200 characters. Logged in the anti-dump audit trail. Example: \"User asked me to summarize last week's migration decisions.\"",
-  "type": "string"
-}

removedInput schema / properties / scope

Removed value: -{
-  "description": "Explicit memory scope. \"agent\" (default, fail-closed) = limits recall to the given agent_id (or the token agent). \"tenant\" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, \"agent\" is inferred; if both omitted, the token agent is used with a warning.",
-  "enum": [
-    "agent",
-    "tenant"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "query",
-  "reason"
-]New value: +[
+  "query"
+]

Changed2 schema fields changedApr 24, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED (MEMORY_EXPORT_GOVERNANCE_V1): human-readable justification for retrieving PLAINTEXT memory content. Must be 10–200 characters. Logged in the anti-dump audit trail. Example: \"User asked me to summarize last week's migration decisions.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "reason"
+]

Changed2 schema fields changedApr 23, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Agent identifier to scope memory recall. Defaults to \"default\"."New value: +"Agent identifier (canonical or alias). Used only when scope=\"agent\" or scope is inferred."

addedInput schema / properties / scope

Added value: +{
+  "description": "Explicit memory scope. \"agent\" (default, fail-closed) = limits recall to the given agent_id (or the token agent). \"tenant\" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, \"agent\" is inferred; if both omitted, the token agent is used with a warning.",
+  "enum": [
+    "agent",
+    "tenant"
+  ],
+  "type": "string"
+}

Changed1 schema field changedApr 17, 2026

addedInput schema / properties / mode

Added value: +{
+  "description": "Recall routing mode. \"temporal\" = pure chronological, \"semantic\" = FTS + TQ ranking, \"priority\" = critical/high-TQ first, \"hybrid\" = weighted blend, \"auto\" = detect from query (default).",
+  "enum": [
+    "auto",
+    "temporal",
+    "semantic",
+    "priority",
+    "hybrid"
+  ],
+  "type": "string"
+}

First observedApr 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds valuable behavioral context beyond this: the mandatory 'reason' parameter with character range, the governance/audit policy implication, and the 20/min rate limit. This is meaningful additional disclosure of operational constraints.

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 concise sentences with no filler. The core action is front-loaded, followed immediately by the critical governance constraint and rate limit. Every phrase earns its place and the structure is easily scannable.

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 return format and parameter semantics are already documented. However, the description lacks context about the fail-closed scope behavior and, more importantly, does not disambiguate from the 'recall_memory' sibling, leaving a notable completeness gap for an AI agent selecting between tools.

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 the schema already provides rich semantics for each parameter, including enums and examples. The description's mention of 'reason (10–200 chars)' reinforces the schema but does not add significant new meaning beyond what the parameter descriptions already state. Baseline 3 is appropriate.

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 ('Retrieve') and resource ('persisted memory') along with routing modes, which clearly identifies the tool's function. However, the sibling tool 'recall_memory' exists with a nearly identical name, and the description does not differentiate this tool from it, so it is not a 5.

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

Usage Guidelines2/5

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

The description explains governance and rate limits but gives no guidance on when to use 'recall' versus the closely related 'recall_memory', 'search', or 'list_memories' siblings. There is no mention of conditions, exclusions, or alternative routing, leaving the agent to infer usage from the name and schema.

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

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

B3.1/5.0

Disambiguation2/5

Several tools are redundant: recall_memory is explicitly an alias of recall, and save_memory/save_to_synapse/store_memory all persist memories. This makes the tool boundary unclear for agents choosing between them, even though core operations like health_check and slo_report are distinct.

Naming Consistency2/5

Names are consistently snake_case, but verb usage is inconsistent: save_memory, save_to_synapse, and store_memory use different verbs for the same operation, and recall/recall_memory add an alias rather than following one convention. The pattern is readable but not predictable.

Tool Count3/5

Thirteen tools is not inherently excessive for an agent-memory/trust service, but the presence of multiple aliases inflates the surface and means not every tool earns its place. The effective set is smaller, making the count feel padded.

Completeness3/5

The surface covers initialization, save, list, search/recall, feedback, and handover, but there is no update or delete operation for memories. This leaves lifecycle management incomplete and may force agents to work around missing state-management operations.

recall

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources