Synapse Layer — Trust Infrastructure for AI Agents

save_to_synapse

Idempotent

Persist memory with encryption at rest, sanitization, and deduplication controls.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Tags for categorization.
`type`	No	Event type: [MILESTONE], [DECISION], [ALERT], [AUTO-STRAT], [AUTO-OP], [AUTO-INSIGHT], [AUTO-DECISION], [AUTO-CONTEXT], [MANUAL].
`content`	Yes	The memory content to store securely.
`project`	No	Project identifier (e.g., SYNAPSE_LAYER).
`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".
`importance`	No	Accepted for compatibility; not enforced by the API.
`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

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`memory_id`	Yes
`trust_quotient`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / importance / description

Previous value: -"Importance level 1–5 (default: 3)."New value: +"Accepted for compatibility; not enforced by the API."

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"
+}

Changed7 schema fields changedAug 29, 2026

removedOutput schema / properties / id

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

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

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 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"
+}

First observedApr 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false (mutation) and idempotentHint=true (safe to call multiple times). The description adds 'encryption at rest, sanitization, and deduplication controls' which are behavioral traits not in annotations. However, it does not disclose that force_intent and intent_reason are used for manual override and ignored otherwise, which is only in the parameter descriptions. No contradiction found.

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 sentence, succinct and front-loaded with the core purpose. It includes secondary features without verbosity. It is concise, but could be slightly more structured to list the controls, though it is acceptable.

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?

Given the tool's complexity (9 params, manual override logic, multiple intent types) and the high schema coverage, the description does not fully explain when to use force_intent or the implications of the 'subject' field for isolation. The annotations cover idempotency and mutation, but the description lacks guidance on error handling or warnings. An output schema exists but no return format is mentioned, so it is partially complete.

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 schema already documents each parameter. The description adds some context about encryption and controls but does not explain parameter syntax beyond that. The subject parameter has detailed semantics in the schema, and the description does not add more. 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?

The description states the verb 'persist' and the resource 'memory' with secondary controls (encryption, sanitization, deduplication). It does not differentiate from siblings like save_memory/store_mory, but it is clear enough. A higher score would require mentioning that this is the primary persistence tool while siblings are aliases or variations.

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?

No explicit guidance on when to use this tool versus save_memory, store_memory, or other siblings. The description implies general use for persisting memory but does not mention exclusions, such as when to use recall or process_text. It also lacks context about the manual override scenario, which is only partially addressed in the parameter description.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

save_to_synapse

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources