Skip to main content
Glama
Sign In

Synapse Layer — Trust Infrastructure for AI Agents

by io.github.SynapseLayer
OverviewDiscussionsAdmin

neural_handover

Transfer contextual state between agents with continuity controls.

Input Schema

NameRequiredDescriptionDefault
tokenYesThe handover token (64 hex chars). Generated by the source agent/user in Forge UI.
reasonYesREQUIRED (10–200 chars). Human-readable justification for consuming this handover. Example: "Receiving project context from Claude session."
project_idNoProject ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
consuming_agentNoAgent identifier consuming the handover (defaults to token agent).

Output Schema

NameRequiredDescriptionDefault
successYes
memoriesNo
fromAgentNo
handoverIdYes
memoryCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / fromAgent
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / memories
      Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / memoryCount
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / status
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / success
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / required
      Previous value: -[
-  "status"
-]New value: +[
+  "success",
+  "handoverId"
+]
  2. Changed1 schema field 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"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "handoverId": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "fromAgent": {
-      "type": "string"
-    },
-    "handoverId": {
-      "type": "string"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "agent": {
-            "type": "string"
-          },
-          "category": {
-            "type": "string"
-          },
-          "content": {
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "memoryCount": {
-      "type": "number"
-    },
-    "success": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "success"
-  ],
-  "type": "object"
-}New value: +null
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "fromAgent": {
+      "type": "string"
+    },
+    "handoverId": {
+      "type": "string"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "content": {
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "memoryCount": {
+      "type": "number"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  6. Added

TDQS

C2.6/5.0
Behavior2/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 mutates local state, but the description adds nothing about token consumption semantics — whether a token is single-use, what state gets transferred or overwritten, or what authorization project_id implies. For a state-transfer operation with real side effects, that silence leaves the agent unable to predict consequences.

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?

It is a single short sentence with the operation front-loaded, so there is no wasted text or buried lead. Brevity here shades into under-specification rather than padding.

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?

An output schema exists so return values need no explanation, but for a mutation tool that consumes a security-sensitive token, the description omits what state is transferred, the lifecycle of the token, and any authorization requirements. The agent has to reconstruct the workflow from parameter descriptions alone.

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 every parameter is already documented with format and length constraints, establishing the baseline of 3. The description contributes no additional parameter meaning beyond what the schema states.

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 'Transfer' and object 'contextual state between agents' give a rough sense of the operation, but 'with continuity controls' is undefined jargon that never resolves what is actually moved or produced. Nothing in the sentence distinguishes it from siblings such as initialize_context or recall, which plausibly serve adjacent context-passing purposes.

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 statement of when this tool should be chosen over initialize_context, recall, or save_memory, and no mention of the precondition that a handover token must already exist (only the schema reveals that). An agent must infer the triggering scenario 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 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