Skip to main content
Glama
Sign In

Synapse Layer — Trust Infrastructure for AI Agents

by io.github.SynapseLayer
OverviewDiscussionsAdmin

initialize_context

Read-only

Initialize a persistent memory context for a conversation or agent session. Returns REDACTED metadata by default (detail="summary"). Use detail="full" with a reason (10–200 chars) to retrieve plaintext content under MEMORY_EXPORT_GOVERNANCE_V1.

Input Schema

NameRequiredDescriptionDefault
detailNoDetail level. "summary" (default) = redacted metadata only, no plaintext. "full" = plaintext content; REQUIRES the reason parameter and is audit-logged.
reasonNoREQUIRED only when detail="full" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail="full" WILL fail with code -32602.
project_idNoOptional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
scopeNo
agent_idNo
memoriesNo
initializedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / error
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / initialized
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / required
      Previous value: -[
-  "scope"
-]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Optional project ID. Required for Corporate context unless the token is project-bound.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "memories": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "scope"
+  ],
+  "type": "object"
+}
  4. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • removedInput schema / properties / detail
      Removed value: -{
-  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
-  "enum": [
-    "summary",
-    "full"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / reason
      Removed value: -{
-  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
-  "type": "string"
-}
  6. Changed3 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "error": {
-      "description": "Present only on fail-closed path.",
-      "type": "string"
-    },
-    "initialized": {
-      "type": "boolean"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "query": {
-      "type": "string"
-    },
-    "scope": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "initialized",
-    "count",
-    "memories"
-  ],
-  "type": "object"
-}New value: +null
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "error": {
+      "description": "Present only on fail-closed path.",
+      "type": "string"
+    },
+    "initialized": {
+      "type": "boolean"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "initialized",
+    "count",
+    "memories"
+  ],
+  "type": "object"
+}
  8. Added
  9. Removed
  10. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is read-only and closed-world, and the description adds useful behavioral context: it returns redacted metadata by default and only exposes plaintext under the MEMORY_EXPORT_GOVERNANCE_V1 policy when detail="full" is used with a reason. It does not itself mention audit logging, though the schema does.

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 two tightly written sentences with the core behavior front-loaded. Every sentence carries necessary information about default redaction and the gated plaintext path, with no waste.

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 that there is an output schema and complete parameter descriptions, the description supplies the key behavioral and privacy context an agent needs. It is nearly complete, though it could be stronger if it clarified when this tool should be preferred over sibling memory-access 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%, so the parameters are already fully documented in the input schema. The description reinforces the default detail="summary" and the reason requirement for detail="full", but it adds no semantic detail beyond what the schema already provides.

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: initializing a persistent memory context for a conversation or agent session. It is clear what the tool does, but it does not explicitly distinguish this initialization step from sibling memory tools such as recall or list_memories.

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?

It implies the tool is used at the start of a conversation or agent session and gives guidance for detail="full" versus the default redacted mode. However, it does not say when to use initialize_context instead of sibling tools like recall, search, or list_memories, leaving the agent to infer that usage.

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 toolsInspect
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.

Resources