Synapse Layer — Trust Infrastructure for AI Agents

store_memory

Idempotent

Store structured memory with metadata and trust scoring.

Input Schema

Name	Required	Description
`tags`	No	Tags for categorization.
`content`	Yes	The memory content to store securely.
`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 for memory isolation. Defaults to "default".
`project_id`	No	Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
`visibility`	No	private (default) or project (visible to active members of this project).
`force_intent`	No	MANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference \| fact \| procedural \| bio \| critical \| operational \| strategic \| compliance \| security \| system_directive \| clinical \| general \| ephemeral. Se não tiver certeza, NÃO preencha este campo — o sistema classifica automaticamente. Valores não reconhecidos são ignorados silenciosamente e retornados em warnings.
`intent_reason`	No	Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.

Output Schema

Name	Required	Description	Default
`quota`	No
`intent`	No
`status`	Yes
`pipeline`	No
`memory_id`	Yes
`sanitized`	No
`trust_quotient`	No
`privacy_applied`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 29, 2026

removedOutput schema / properties / id

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / intent
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / memory_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / pipeline
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / privacy_applied
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / quota
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / sanitized
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / scope

Removed value: -{
-  "enum": [
-    "agent",
-    "tenant"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / stored

Removed value: -{
-  "type": "boolean"
-}

addedOutput schema / properties / trust_quotient
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "stored",
-  "scope"
-]New value: +[
+  "memory_id",
+  "status"
+]

Changed2 schema fields changedOct 29, 2026

addedInput schema / properties / project_id

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

addedInput schema / properties / visibility

Added value: +{
+  "description": "private (default) or project (visible to active members of this project).",
+  "enum": [
+    "private",
+    "project"
+  ],
+  "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"
+}

Changed2 schema fields changedAug 18, 2026

changedInput schema / properties / force_intent / description

Previous value: -"Override automatic intent classification. When set, the system skips auto-classification and uses this value directly. Accepted values: preference, fact, procedural, bio, critical, operational, strategic, compliance, security, system_directive, clinical, general, ephemeral."New value: +"MANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference | fact | procedural | bio | critical | operational | strategic | compliance | security | system_directive | clinical | general | ephemeral. Se não tiver certeza, NÃO preencha este campo — o sistema classifica automaticamente. Valores não reconhecidos são ignorados silenciosamente e retornados em warnings."

removedInput schema / properties / force_intent / enum

Removed value: -[
-  "preference",
-  "fact",
-  "procedural",
-  "bio",
-  "critical",
-  "operational",
-  "strategic",
-  "compliance",
-  "security",
-  "system_directive",
-  "clinical",
-  "general",
-  "ephemeral"
-]

Changed2 schema fields changedAug 18, 2026

addedInput schema / properties / force_intent

Added value: +{
+  "description": "Override automatic intent classification. When set, the system skips auto-classification and uses this value directly. Accepted values: preference, fact, procedural, bio, critical, operational, strategic, compliance, security, system_directive, clinical, general, ephemeral.",
+  "enum": [
+    "preference",
+    "fact",
+    "procedural",
+    "bio",
+    "critical",
+    "operational",
+    "strategic",
+    "compliance",
+    "security",
+    "system_directive",
+    "clinical",
+    "general",
+    "ephemeral"
+  ],
+  "type": "string"
+}

addedInput schema / properties / intent_reason

Added value: +{
+  "description": "Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.",
+  "maxLength": 500,
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    },
+    "stored": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "id",
+    "stored",
+    "scope"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "intent": {
-      "type": "string"
-    },
-    "memory_id": {
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "pipeline": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "privacy_applied": {
-      "type": "boolean"
-    },
-    "quota": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "sanitized": {
-      "type": "boolean"
-    },
-    "status": {
-      "description": "'saved' on success; 'error' with a message on rejected input.",
-      "type": "string"
-    },
-    "timestamp": {
-      "type": "string"
-    },
-    "trust_quotient": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "status"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "intent": {
+      "type": "string"
+    },
+    "memory_id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "pipeline": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "privacy_applied": {
+      "type": "boolean"
+    },
+    "quota": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "sanitized": {
+      "type": "boolean"
+    },
+    "status": {
+      "description": "'saved' on success; 'error' with a message on rejected input.",
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    },
+    "trust_quotient": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

AddedApr 28, 2026
RemovedApr 27, 2026
AddedApr 23, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds almost nothing beyond that: it doesn't explain what "trust scoring" does, what happens on duplicate content (despite idempotentHint), or the isolation consequences of subject/project_id/visibility — all of which matter for a write tool.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity borders on under-specification for an 8-parameter write tool.

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

Completeness2/5

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

For a mutation tool with 8 parameters, isolation scoping, and a visibility model, one sentence is not enough. An output schema exists so return values needn't be described, but the description never addresses scoping, deduplication, or authorization context (project_id requirements) that an agent must understand before writing.

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 parameter docs are unusually rich (subject token format, visibility enum, force_intent override semantics), so the schema carries the burden. The description adds no parameter meaning of its own; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb and resource are clear ("Store ... memory"), but "structured memory" and "trust scoring" are never explained, and the description gives no way to distinguish it from close siblings like save_memory or save_to_synapse. An agent reading only the description cannot tell which store path to pick.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative among the many overlapping siblings (save_memory, save_to_synapse, recall_memory). Usage must be inferred entirely from the name.

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.

store_memory

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources