Skip to main content
Glama
Sign In

Synapse Layer — Trust Infrastructure for AI Agents

by io.github.SynapseLayer
OverviewDiscussionsAdmin

memory_feedback

Submit feedback to adjust trust scoring for stored memories.

Input Schema

NameRequiredDescriptionDefault
signalYesFeedback signal: used (auto), helpful (positive), irrelevant (negative), ignored.
memoryIdNoDeprecated camelCase alias of memory_id — still accepted for backward compatibility.
memory_idNoID of the memory to provide feedback on (canonical snake_case name).
sessionIdNoDeprecated camelCase alias of session_id — still accepted for backward compatibility.
project_idNoProject ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
session_idNoOptional session identifier for tracking (canonical snake_case name).

Output Schema

NameRequiredDescriptionDefault
signalNo
successYes
memoryIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed5 schema fields changed
    • removedOutput schema / properties / applied
      Removed value: -{
-  "type": "boolean"
-}
    • addedOutput schema / properties / signal
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / success
      Added value: +{
+  "type": "boolean"
+}
    • removedOutput schema / properties / trust
      Removed value: -{
-  "type": "number"
-}
    • changedOutput schema / required
      Previous value: -[
-  "memoryId",
-  "applied"
-]New value: +[
+  "memoryId",
+  "success"
+]
  3. Changed6 schema fields changed
    • changedInput schema / properties / memoryId / description
      Previous value: -"ID of the memory to provide feedback on."New value: +"Deprecated camelCase alias of memory_id — still accepted for backward compatibility."
    • addedInput schema / properties / memory_id
      Added value: +{
+  "description": "ID of the memory to provide feedback on (canonical snake_case name).",
+  "type": "string"
+}
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional session identifier for tracking."New value: +"Deprecated camelCase alias of session_id — still accepted for backward compatibility."
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Optional session identifier for tracking (canonical snake_case name).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "memoryId",
-  "signal"
-]New value: +[
+  "signal"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "applied": {
+      "type": "boolean"
+    },
+    "memoryId": {
+      "type": "string"
+    },
+    "trust": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "memoryId",
+    "applied"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "memoryId": {
-      "type": "string"
-    },
-    "signal": {
-      "enum": [
-        "used",
-        "ignored",
-        "helpful",
-        "irrelevant"
-      ],
-      "type": "string"
-    },
-    "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": {
+    "memoryId": {
+      "type": "string"
+    },
+    "signal": {
+      "enum": [
+        "used",
+        "ignored",
+        "helpful",
+        "irrelevant"
+      ],
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  6. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a mutation (readOnlyHint=false) with no external side effects (openWorldHint=false), and the description adds the one useful fact beyond that: the write adjusts trust scoring rather than storing content. It does not disclose whether feedback is cumulative, idempotent, or reversible, nor the authorization implication of project_id, so it adds only modest context over the annotations.

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; the purpose appears in the first few words. It is efficient, though at this brevity it leaves no room for the usage or behavioral detail the tool arguably needs.

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?

An output schema exists, so return values need not be described, and the schema fully documents parameters including deprecated aliases. What remains missing is behavior an agent needs for a scoring mutation: whether repeated signals stack, who may submit feedback on a given memory, and what the caller observes afterward.

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 enum values are individually explained in the schema, so parameters are fully self-documenting. The description adds no parameter semantics of its own, which is the expected baseline of 3 when the schema carries the load.

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?

Specific verb ('Submit feedback') plus the target of the effect ('trust scoring for stored memories'), which clearly separates it from read siblings like recall/list_memories and from plain writes like save_memory. It stops short of naming any sibling as an alternative, so it lands at 4 rather than 5.

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?

The description gives no when-to-use guidance, no preconditions, and no routing to alternatives — nothing tells the agent when to call this versus simply calling save_memory again. Any usage semantics live entirely in the schema's enum descriptions, not in the tool 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 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