Skip to main content
Glama
Sign In

Synapse Layer — Trust Infrastructure for AI Agents

by io.github.SynapseLayer
OverviewDiscussionsAdmin

process_text

Extract candidate memories from free-form text with governance filters and sanitization.

Input Schema

NameRequiredDescriptionDefault
textYesFree-form text to scan for auto-save triggers.
sourceNoSource identifier (default: mcp).
projectNoForce a specific project namespace. Auto-detected if omitted.
agent_idNoAgent identifier. Defaults to "default".
project_idNoProject ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
visibilityNoprivate (default) or project (visible to active members of this project).

Output Schema

NameRequiredDescriptionDefault
extractedYes
storedCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Force a specific project (e.g., SYNAPSE_LAYER, OFFLY). Auto-detected if omitted."New value: +"Force a specific project namespace. Auto-detected if omitted."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "extracted": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "storedCount": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "extracted",
+    "storedCount"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "events_detected": {
-      "type": "number"
-    },
-    "message": {
-      "type": "string"
-    },
-    "pipeline": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "results": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "intent": {
-            "type": "string"
-          },
-          "memory_id": {
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "status": {
-      "description": "'processed' on success; 'error' with a message on rejected input.",
-      "type": "string"
-    },
-    "timestamp": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "status"
-  ],
-  "type": "object"
-}New value: +null
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "events_detected": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "pipeline": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "intent": {
+            "type": "string"
+          },
+          "memory_id": {
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "'processed' on success; 'error' with a message on rejected input.",
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  6. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent knows this is a non-read-only, closed-world operation. The description adds 'governance filters and sanitization' as behavioral context, but does not explain what state changes occur or what permissions are required.

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 a single, front-loaded sentence with no redundant or filler content. Every part of the sentence conveys useful information.

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 six parameters, an output schema, and annotations covering safety, the description is minimally adequate. However, it does not clarify the mutating side effects implied by readOnlyHint=false or how this tool relates to save_memory, leaving gaps for an agent to infer.

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 all six parameters in detail. The description does not add any parameter semantics beyond what the schema 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 (extract), resource (candidate memories), and source (free-form text) with additional context (governance filters and sanitization). It implies a distinction from saving tools by using 'candidate', but does not explicitly name a sibling tool for differentiation.

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 guidance is provided on when to use this tool versus alternatives such as save_memory or store_memory. The implied usage is only that it processes text, but there are no explicit conditions or exclusions.

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