Synapse Layer — Trust Infrastructure for AI Agents

Name: Synapse Layer — Trust Infrastructure for AI Agents
Author: SynapseLayer

by io.github.SynapseLayer

Overview Discussions Admin

Server Details

MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.

Ownership verified

Status: Healthy
Uptime: 99.1% over 75 days
Last Tested: 2026-11-03 18:59
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: SynapseLayer/synapse-layer
GitHub Stars: 13
Server Listing: synapse-layer
ChatGPT: –
Claude: –

TDQS

C2.8/5.0

Scored 2026-10-29 19:55 across 13 tools

Disambiguation2/5

Four tools are explicitly duplicative: recall/recall_memory and save_memory/save_to_synapse are documented aliases, and store_memory overlaps heavily with save_to_synapse (both persist memory with metadata/trust). Retrieval is also split three ways between recall (semantic/temporal/hybrid), search (full-text), and list_memories, forcing the agent to reason about subtle distinctions rather than picking a clearly distinct tool.

Naming Consistency2/5

Conventions are mixed: bare verbs (recall, search), verb_noun (save_memory, store_memory, list_memories, process_text, health_check), noun_verb (memory_feedback), and noun_noun (neural_handover, slo_report). Alias pairs also use different naming styles for the same operation (recall vs recall_memory, save_memory vs save_to_synapse).

Tool Count3/5

13 tools is nominally within a reasonable range, but three of them exist only as aliases of other tools, so the effective surface is closer to 10 and the extra entries add selection noise rather than capability.

Completeness3/5

Write, read, search, extraction, feedback, and handover are all covered, but there is no delete/forget or update/expire operation, which are core lifecycle gaps for a persistent memory store. There is also no direct get-by-ID, leaving list+recall as the only path to a specific record.

Available Tools

13 tools

health_checkA

Read-only

Inspect

Check service availability, engine version, and storage health. Public method.

Name	Required	Description	Default
No parameters

Output Schema

Name	Required	Description
`status`	Yes
`version`	Yes
`latencyMs`	No
`dbRealLatencyMs`	No

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that with 'Public method', signalling no auth/credential prerequisite, which an agent otherwise could not infer. It does not mention rate limits or latency, but that is a minor gap given the read-only annotation.

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?

Two short sentences, zero filler. The scope is front-loaded and the access qualifier follows, so the agent can decide to call it after the first clause.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the description names the three areas reported. What is missing is a hint about when a degraded result matters or whether repeated polling is acceptable, which for a trivial zero-param health endpoint is a small omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameter semantics.

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?

States a specific verb ('Check') and the exact dimensions inspected: service availability, engine version, storage health. That is far more concrete than a generic 'health check', and the nature of the tool makes sibling confusion unlikely without needing to name one explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Public method' implies it can be called without authentication, and 'health check' implies diagnostic use, but the description never says when to prefer it (e.g. before bulk operations or on connection failures) or what to do with the result. Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

initialize_contextA

Read-only

Inspect

Initialize a persistent memory context for a conversation or agent session. Returns REDACTED metadata by default (detail="summary"). Use detail="full" with a reason (10–200 chars) to retrieve plaintext content under MEMORY_EXPORT_GOVERNANCE_V1.

Name	Required	Description
`detail`	No	Detail level. "summary" (default) = redacted metadata only, no plaintext. "full" = plaintext content; REQUIRES the reason parameter and is audit-logged.
`reason`	No	REQUIRED only when detail="full" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail="full" WILL fail with code -32602.
`project_id`	No	Optional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description
`count`	No
`error`	No
`scope`	No
`agent_id`	No
`memories`	No
`initialized`	No

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish that this is read-only and closed-world, and the description adds useful behavioral context: it returns redacted metadata by default and only exposes plaintext under the MEMORY_EXPORT_GOVERNANCE_V1 policy when detail="full" is used with a reason. It does not itself mention audit logging, though the schema does.

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 two tightly written sentences with the core behavior front-loaded. Every sentence carries necessary information about default redaction and the gated plaintext path, with no waste.

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

Completeness4/5

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

Given that there is an output schema and complete parameter descriptions, the description supplies the key behavioral and privacy context an agent needs. It is nearly complete, though it could be stronger if it clarified when this tool should be preferred over sibling memory-access tools.

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 parameters are already fully documented in the input schema. The description reinforces the default detail="summary" and the reason requirement for detail="full", but it adds no semantic detail beyond what the schema already 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 and resource: initializing a persistent memory context for a conversation or agent session. It is clear what the tool does, but it does not explicitly distinguish this initialization step from sibling memory tools such as recall or list_memories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is used at the start of a conversation or agent session and gives guidance for detail="full" versus the default redacted mode. However, it does not say when to use initialize_context instead of sibling tools like recall, search, or list_memories, leaving the agent to infer that usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_memoriesB

Read-only

Inspect

List memory metadata with pagination and governance limits.

Name	Required	Description
`limit`	No	Maximum memory metadata rows to return. Hard-capped: default 5, max 10. Values above 10 are silently reduced to 10.
`scope`	No	Explicit memory scope. "agent" (default, fail-closed) = lists memories for the given agent_id (or the token agent). "tenant" = lists memories across all agents of the authenticated tenant.
`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 (canonical or alias). Used only when scope="agent" or scope is inferred.
`project_id`	No	Optional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description
`count`	Yes
`total`	No
`memories`	Yes

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the notion of governance limits but does not disclose anything concrete beyond that, leaving the hard-cap behavior to the schema rather than expanding on it.

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 front-loaded sentence with no waste. It is efficient but borderline terse, devoting no room to any usage or behavioral guidance.

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?

With an output schema present and 100% schema coverage, the structured data carries most of the burden. The description is minimally adequate but thin given the tool has five parameters and numerous sibling alternatives it doesn't help the agent choose between.

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 fully documented (including the limit hard-cap and scope enum semantics). The description only gestures at "pagination and governance limits" without adding syntax or default detail beyond the schema, so the baseline 3 applies.

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 and resource ("List memory metadata") plus scoping (pagination and governance limits), so an agent knows this enumerates metadata rather than retrieving content. It does not, however, differentiate itself from siblings like recall, recall_memory, or search, leaving the metadata-vs-content distinction implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the word "metadata" hints this is for listing/enumeration rather than content retrieval, and "governance limits" suggests constrained listing. There is no explicit when-to-use, when-not-to-use, or named alternative among the many recall/search siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

memory_feedbackBInspect

Submit feedback to adjust trust scoring for stored memories.

Name	Required	Description
`signal`	Yes	Feedback signal: used (auto), helpful (positive), irrelevant (negative), ignored.
`memoryId`	No	Deprecated camelCase alias of memory_id — still accepted for backward compatibility.
`memory_id`	No	ID of the memory to provide feedback on (canonical snake_case name).
`sessionId`	No	Deprecated camelCase alias of session_id — still accepted for backward compatibility.
`project_id`	No	Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
`session_id`	No	Optional session identifier for tracking (canonical snake_case name).

Output Schema

Name	Required	Description
`signal`	No
`success`	Yes
`memoryId`	Yes

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.

neural_handoverCInspect

Transfer contextual state between agents with continuity controls.

Name	Required	Description
`token`	Yes	The handover token (64 hex chars). Generated by the source agent/user in Forge UI.
`reason`	Yes	REQUIRED (10–200 chars). Human-readable justification for consuming this handover. Example: "Receiving project context from Claude session."
`project_id`	No	Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
`consuming_agent`	No	Agent identifier consuming the handover (defaults to token agent).

Output Schema

Name	Required	Description
`success`	Yes
`memories`	No
`fromAgent`	No
`handoverId`	Yes
`memoryCount`	No

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.

process_textBInspect

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

Name	Required	Description
`text`	Yes	Free-form text to scan for auto-save triggers.
`source`	No	Source identifier (default: mcp).
`project`	No	Force a specific project namespace. Auto-detected if omitted.
`agent_id`	No	Agent identifier. 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).

Output Schema

Name	Required	Description
`extracted`	Yes
`storedCount`	Yes

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.

recallA

Read-only

Inspect

Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min.

Name	Required	Description
`mode`	No	Recall routing mode. "temporal" = pure chronological, "semantic" = FTS + TQ ranking, "priority" = critical/high-TQ first, "hybrid" = weighted blend, "auto" = detect from query (default).
`limit`	No	Maximum memories to return (1–50, default: 10).
`query`	Yes	What to recall — natural language query for memory retrieval.
`scope`	No	Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, "agent" is inferred; if both omitted, the token agent is used (verified-token scope).
`reason`	Yes	REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: "User asked me to summarize last week decisions."
`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 (canonical or alias). Used only when scope="agent" or scope is inferred.
`project_id`	No	Optional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description
`count`	Yes
`scope`	Yes
`memories`	Yes

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful non-schema behavioral context: a required audit reason and a rate limit of 20/min. It does not contradict 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no waste. The core purpose is front-loaded, followed immediately by governance and rate-limit constraints.

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

Completeness4/5

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

The description covers purpose, governance, and rate limits, and the schema plus output schema carry the detailed parameter and return-value semantics. It is sufficient to call the tool correctly, though it still lacks sibling differentiation and explicit usage guidance.

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 input schema already documents all eight parameters in detail. The description restates the reason requirement and mentions routing modes, but adds little parameter meaning beyond the schema.

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 and resource: retrieve relevant persisted memory. It also names routing modes, making the retrieval purpose clear. However, it does not distinguish this tool from close siblings such as recall_memory or search.

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 explicit guidance on when to use this tool versus recall_memory, search, list_memories, or other retrieval siblings. It implies a memory-recall use case but provides no selection criteria or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

recall_memoryA

Read-only

Inspect

Recall persisted memory by query. Alias of recall.

Name	Required	Description
`mode`	No	Recall routing mode.
`limit`	No	Maximum memories to return (1–50, default: 10).
`query`	Yes	What to recall — natural language query for memory retrieval.
`scope`	No	Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, "agent" is inferred; if both omitted, the token agent is used (verified-token scope).
`reason`	Yes	REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Without this the call WILL fail with code -32602. Example: "Checking user project status."
`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 (canonical or alias). Used only when scope="agent" or scope is inferred.
`project_id`	No	Optional project ID. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description
`count`	Yes
`scope`	Yes
`memories`	Yes

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety behavior is covered. The description adds only that memory is persisted and that this is an alias of recall; it does not mention the required audit reason or fail-closed scope behavior, though the schema does.

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?

Two short sentences, front-loaded with the core purpose and followed by the alias note. There is no wasted verbiage.

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

Completeness4/5

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

The rich input schema, output schema, and annotations cover most operational details. The description is sufficient to identify the tool as an alias of recall, though it could better explain routing versus the recall sibling.

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 explains the eight parameters in detail. The description mentions only the query concept and does not add meaning beyond the structured parameter definitions.

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?

States a specific verb and resource: 'Recall persisted memory by query.' The added 'Alias of recall' identifies the relationship to a sibling, but does not explain why this alias exists or when it should be preferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names 'recall' as an equivalent tool, which implies interchangeable use, but gives no explicit when-to-use guidance versus recall, list_memories, or search. The routing is left implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save_memoryA

Idempotent

Inspect

Save a memory entry to the persistent store. Alias of save_to_synapse.

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.
`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
`quota`	No
`intent`	No
`status`	Yes
`pipeline`	No
`memory_id`	Yes
`sanitized`	No
`trust_quotient`	No
`privacy_applied`	No

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare that this is a write operation, not read-only, not open-world, and idempotent. The description adds that the store is persistent and that the tool is an alias, but does not add much beyond that about visibility, authorization, or return behavior.

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 two short sentences with the core action front-loaded and no wasted text. The alias relationship is stated immediately after the purpose.

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 and the input schema is fully described, so much of the contextual burden is covered elsewhere. Still, for an eight-parameter write tool with isolation semantics, the description is minimal and does not clarify when to use this alias versus sibling memory-save tools.

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 all eight parameters are documented in the schema, including subject isolation, project_id, visibility, and force_intent. The description does not add parameter-level meaning beyond the schema, so the baseline of 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 uses a specific verb and resource: "Save a memory entry to the persistent store." It also identifies the tool as an alias of save_to_synapse, which helps relate it to a sibling, though it does not distinguish it from store_memory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The alias relationship to save_to_synapse gives implied usage guidance for choosing between equivalent save tools. However, there are no explicit conditions for when to use this versus store_memory or save_to_synapse, and no exclusions or prerequisites are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save_to_synapseB

Idempotent

Inspect

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

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.
`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
`status`	Yes
`memory_id`	Yes
`trust_quotient`	No

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and openWorldHint=false; the description adds useful context that writes are encrypted at rest and sanitized, which is not in the annotations. However, 'deduplication controls' is vague — it never says what actually happens on a duplicate (skip, merge, overwrite), which is the key behavioral question for a non-destructive-but-idempotent write.

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 zero filler, and the core action leads. It is arguably too terse for an 11-parameter tool, but nothing in it is wasted.

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 and annotations cover the safety profile, which lowers the burden. Still, for a write tool with 11 parameters involving memory isolation (subject, agent_id, project_id, visibility) and deduplication semantics, one sentence leaves significant conceptual gaps that the schema alone doesn't resolve.

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 all 11 parameters are documented in the schema and the baseline is 3. The description adds no parameter-level meaning at all, and in particular does nothing to disambiguate the confusingly overlapping 'project' vs 'project_id' pair or the isolation implications of 'subject'/'agent_id'.

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?

States a specific verb ('Persist memory') and resource, and adds the distinguishing traits (encryption at rest, sanitization, deduplication). It never distinguishes itself from the very similar siblings save_memory and store_memory, so an agent cannot tell which write tool to prefer from the description alone.

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 guidance on when to use this versus save_memory, store_memory, or list_memories, and no stated prerequisites (e.g. project_id needed for Corporate context). The reader is left to infer everything about selection from the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchB

Read-only

Inspect

Search persisted memory across agent scopes using full-text matching. Governance: requires reason (10–200 chars) because results contain plaintext content.

Name	Required	Description
`limit`	No	Maximum results to return (1–50, default: 20).
`query`	Yes	Search query — natural language or keywords.
`scope`	No	Explicit search scope. "agent" (default, fail-closed) = limits search to the given agent_id (or the token agent). "tenant" = cross-agent search within the authenticated tenant. If omitted with agent_id present, "agent" is inferred; if both omitted, the token agent is used (verified-token scope).
`reason`	Yes	REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: "Checking prior migration decisions for the user."
`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 (canonical or alias). Used only when scope="agent" or scope is inferred.
`project_id`	No	Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.

Output Schema

Name	Required	Description
`count`	Yes
`scope`	Yes
`results`	Yes

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the governance consequence — a reason of 10–200 chars is mandatory and results carry plaintext content — but that is largely a restatement of the reason parameter's schema text rather than new behavioral disclosure (no pagination, ranking, or failure modes described).

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?

Two sentences, front-loaded with purpose and followed by the single governance constraint. Nothing is padded and the critical compliance rule is placed where it will be read.

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?

With an output schema present, return values need no explanation, but for a 7-parameter search inside a cluster of near-synonymous retrieval tools the description should still explain how it differs from recall/recall_memory/list_memories. That disambiguation is missing.

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 coverage is 100% and the schema already documents scope semantics, limit range, subject token, and the reason constraint in detail. The description repeats the reason length constraint without adding meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (search persisted memory) plus the retrieval mode (full-text matching) and scope dimension (agent scopes). It is clearer than a bare 'search' but never names which sibling (recall, recall_memory, list_memories) it replaces, so an agent still has to infer the boundary.

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 only usage instruction is a governance rule about the reason parameter — there is no statement of when to call this versus list_memories, recall, or recall_memory, nor any exclusion. With four similarly named retrieval siblings, the missing routing guidance is a real gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

slo_reportA

Read-only

Inspect

Return uptime and SLO metrics for the MCP service.

Name	Required	Description	Default
`admin_token`	Yes	Admin authentication token. Must match ADMIN_TOKEN environment variable.
`window_hours`	No	Time windows in hours for the report. Default: [24, 168] (24h + 7d).

Output Schema

Name	Required	Description
`status`	Yes
`version`	No
`windows`	No
`generatedAt`	Yes

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the subject matter (MCP service uptime/SLO); it does not mention the admin-token gate, failure behavior on bad auth, or cost/latency of querying multiple windows, so it adds little beyond structured data.

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 or redundancy. It is efficiently sized, though it borders on terse for a tool with an auth prerequisite and a configurable multi-window parameter.

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

Completeness4/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, and both parameters are fully described in the schema. What remains unaddressed is minor operational context — auth failure modes and whether windows are computed independently — but nothing blocks correct invocation.

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 admin_token's auth requirement and window_hours' default ([24, 168]) are already fully documented in the schema. The description adds no interpretation of the window array (e.g., allowed ranges, granularity returned), so baseline 3 applies.

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?

States a specific verb ("Return") and a specific resource ("uptime and SLO metrics") scoped to the MCP service. An agent can tell exactly what this produces; no sibling differentiation is needed because all listed siblings are memory/text tools with no overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied — an agent infers this is for health/SLO monitoring. There is no explicit when-to-use, when-not-to-use, or pointer to a related tool (e.g., health_check for a lightweight liveness probe vs. this for full metric windows).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

store_memoryC

Idempotent

Inspect

Store structured memory with metadata and trust scoring.

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
`quota`	No
`intent`	No
`status`	Yes
`pipeline`	No
`memory_id`	Yes
`sanitized`	No
`trust_quotient`	No
`privacy_applied`	No

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

6 tool updatesOct 29, 2026

Changedhealth_check3 fields changed
- removedOutput schema / properties / dbLatencyMs
```
Removed value: -{
-  "type": "number"
-}
```
- addedOutput schema / properties / dbRealLatencyMs
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / latencyMs
```
Added value: +{
+  "type": "number"
+}
```
Changedinitialize_context4 fields changed
- addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / initialized
```
Added value: +{
+  "type": "boolean"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "scope"
-]New value: +[]
```

Changedneural_handover6 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"
+]

Changedsave_memory12 fields changed

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

Changedslo_report10 fields changed

removedOutput schema / properties / errorRate
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / generatedAt
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / p50

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

removedOutput schema / properties / p95

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

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

removedOutput schema / properties / uptime

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

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

removedOutput schema / properties / window

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

addedOutput schema / properties / windows

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "uptime"
-]New value: +[
+  "generatedAt",
+  "status"
+]

Changedstore_memory12 fields changed

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

11 tool updatesOct 29, 2026

Changedinitialize_context1 field changed

addedInput schema / properties / project_id

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

Changedlist_memories1 field changed

addedInput schema / properties / project_id

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

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

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

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

Changedrecall1 field changed

addedInput schema / properties / project_id

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

Changedrecall_memory1 field changed

addedInput schema / properties / project_id

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

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

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

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

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

1 tool updateOct 10, 2026

Changedprocess_text1 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."

1 tool updateSep 14, 2026

Changedsave_to_synapse1 field changed

changedInput schema / properties / importance / description

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

7 tool updatesSep 2, 2026

Changedlist_memories1 field changed

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

Changedrecall1 field changed

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

Changedrecall_memory1 field changed

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

Changedsave_memory1 field changed

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

Changedsave_to_synapse1 field changed

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

Changedsearch1 field changed

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

Changedstore_memory1 field changed

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

2 tool updatesAug 29, 2026

Changedmemory_feedback5 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"
+]

Changedsave_to_synapse7 fields changed

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

3 tool updatesAug 18, 2026

Changedsave_memory2 fields changed

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"
-]

Changedsave_to_synapse2 fields changed

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"
-]

Changedstore_memory2 fields changed

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"
-]

3 tool updatesAug 18, 2026

Changedsave_memory2 fields changed

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

Changedsave_to_synapse2 fields changed

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

Changedstore_memory2 fields changed

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

13 tool updatesAug 17, 2026

Changedhealth_check1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dbLatencyMs": {
+      "type": "number"
+    },
+    "status": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "version"
+  ],
+  "type": "object"
+}

Changedinitialize_context1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "memories": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "scope"
+  ],
+  "type": "object"
+}

Changedlist_memories1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

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

Changedneural_handover1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "handoverId": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changedprocess_text1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "extracted": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "storedCount": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "extracted",
+    "storedCount"
+  ],
+  "type": "object"
+}

Changedrecall1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "properties": {
+          "content": {
+            "type": "string"
+          },
+          "createdAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "similarity": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "memories",
+    "count",
+    "scope"
+  ],
+  "type": "object"
+}

Changedrecall_memory1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "properties": {
+          "content": {
+            "type": "string"
+          },
+          "createdAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "similarity": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "memories",
+    "count",
+    "scope"
+  ],
+  "type": "object"
+}

Changedsave_memory1 field changed

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

Changedsave_to_synapse1 field changed

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

Changedsearch1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "results": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "agent",
+        "tenant"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "results",
+    "count",
+    "scope"
+  ],
+  "type": "object"
+}

Changedslo_report1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "errorRate": {
+      "type": "number"
+    },
+    "p50": {
+      "type": "number"
+    },
+    "p95": {
+      "type": "number"
+    },
+    "uptime": {
+      "type": "number"
+    },
+    "window": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "uptime"
+  ],
+  "type": "object"
+}

Changedstore_memory1 field changed

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

2 tool updatesAug 14, 2026

Changedinitialize_context2 fields changed

addedInput schema / properties / detail

Added value: +{
+  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
+  "type": "string"
+}

Changedsearch2 fields changed

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: \"Checking prior migration decisions for the user.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "reason"
+]

2 tool updatesAug 6, 2026

Changedinitialize_context2 fields changed

removedInput schema / properties / detail

Removed value: -{
-  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
-  "enum": [
-    "summary",
-    "full"
-  ],
-  "type": "string"
-}

removedInput schema / properties / reason

Removed value: -{
-  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
-  "type": "string"
-}

Changedsearch2 fields changed

removedInput schema / properties / reason

Removed value: -{
-  "description": "REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: \"Checking prior migration decisions for the user.\"",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "query",
-  "reason"
-]New value: +[
+  "query"
+]

13 tool updatesAug 6, 2026

Changedhealth_check1 field changed

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "cacheAgeMs": {
-      "type": "number"
-    },
-    "cacheHit": {
-      "type": "boolean"
-    },
-    "capabilities": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "database": {
-      "type": "string"
-    },
-    "dbRealLatencyMs": {
-      "type": "number"
-    },
-    "engine": {
-      "type": "string"
-    },
-    "latencyMs": {
-      "type": "number"
-    },
-    "probeThresholds": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "status": {
-      "enum": [
-        "healthy",
-        "degraded",
-        "unhealthy"
-      ],
-      "type": "string"
-    },
-    "timestamp": {
-      "type": "string"
-    },
-    "version": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "status",
-    "version"
-  ],
-  "type": "object"
-}New value: +null

Changedinitialize_context3 fields changed

addedInput schema / properties / detail

Added value: +{
+  "description": "Detail level. \"summary\" (default) = redacted metadata only, no plaintext. \"full\" = plaintext content; REQUIRES the reason parameter and is audit-logged.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED only when detail=\"full\" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail=\"full\" WILL fail with code -32602.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "error": {
-      "description": "Present only on fail-closed path.",
-      "type": "string"
-    },
-    "initialized": {
-      "type": "boolean"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "query": {
-      "type": "string"
-    },
-    "scope": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "initialized",
-    "count",
-    "memories"
-  ],
-  "type": "object"
-}New value: +null

Changedlist_memories1 field changed

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "limit_applied": {
-      "type": "number"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "createdAt": {
-            "description": "ISO-8601 timestamp.",
-            "type": "string"
-          },
-          "id": {
-            "type": "string"
-          },
-          "summary": {
-            "description": "Abstract summary — never plaintext content.",
-            "type": "string"
-          },
-          "tags": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "redacted": {
-      "type": "boolean"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "memories",
-    "count"
-  ],
-  "type": "object"
-}New value: +null

Changedmemory_feedback1 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

Changedneural_handover1 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

Changedprocess_text1 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

Changedrecall1 field changed

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "fallback": {
-      "type": "boolean"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "agent": {
-            "type": "string"
-          },
-          "confidence": {
-            "enum": [
-              "high",
-              "medium_fts",
-              "low"
-            ],
-            "type": "string"
-          },
-          "content": {
-            "description": "Memory content (truncated to 300 chars in recall).",
-            "type": "string"
-          },
-          "hybridScore": {
-            "type": "number"
-          },
-          "id": {
-            "type": "string"
-          },
-          "intent": {
-            "type": "string"
-          },
-          "is_critical": {
-            "type": "boolean"
-          },
-          "memory_type": {
-            "type": "string"
-          },
-          "timestamp": {
-            "description": "ISO-8601 timestamp.",
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "query": {
-      "type": "string"
-    },
-    "queryCacheHit": {
-      "type": "boolean"
-    },
-    "recallLatencyMs": {
-      "type": "number"
-    },
-    "recall_mode": {
-      "type": "string"
-    },
-    "redacted": {
-      "type": "boolean"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    },
-    "sessionCacheHit": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "memories",
-    "count"
-  ],
-  "type": "object"
-}New value: +null

Changedrecall_memory1 field changed

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "fallback": {
-      "type": "boolean"
-    },
-    "memories": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "agent": {
-            "type": "string"
-          },
-          "confidence": {
-            "enum": [
-              "high",
-              "medium_fts",
-              "low"
-            ],
-            "type": "string"
-          },
-          "content": {
-            "description": "Memory content (truncated to 300 chars in recall).",
-            "type": "string"
-          },
-          "hybridScore": {
-            "type": "number"
-          },
-          "id": {
-            "type": "string"
-          },
-          "intent": {
-            "type": "string"
-          },
-          "is_critical": {
-            "type": "boolean"
-          },
-          "memory_type": {
-            "type": "string"
-          },
-          "timestamp": {
-            "description": "ISO-8601 timestamp.",
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "query": {
-      "type": "string"
-    },
-    "queryCacheHit": {
-      "type": "boolean"
-    },
-    "recallLatencyMs": {
-      "type": "number"
-    },
-    "recall_mode": {
-      "type": "string"
-    },
-    "redacted": {
-      "type": "boolean"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    },
-    "sessionCacheHit": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "memories",
-    "count"
-  ],
-  "type": "object"
-}New value: +null

Changedsave_memory1 field changed

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

Changedsave_to_synapse1 field changed

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

Changedsearch3 fields changed

addedInput schema / properties / reason

Added value: +{
+  "description": "REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: \"Checking prior migration decisions for the user.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "reason"
+]

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "agent_id": {
-      "type": "string"
-    },
-    "count": {
-      "type": "number"
-    },
-    "query": {
-      "type": "string"
-    },
-    "results": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "agent": {
-            "type": "string"
-          },
-          "content": {
-            "type": "string"
-          },
-          "intent": {
-            "type": "string"
-          },
-          "is_critical": {
-            "type": "boolean"
-          },
-          "memory_type": {
-            "type": "string"
-          },
-          "timestamp": {
-            "type": "string"
-          },
-          "trust_quotient": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "scope": {
-      "type": "string"
-    },
-    "scope_source": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "results",
-    "count"
-  ],
-  "type": "object"
-}New value: +null

Changedslo_report1 field changed

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "code": {
-      "description": "Error code on admin-auth failure.",
-      "type": "string"
-    },
-    "error": {
-      "description": "Present only on admin-auth failure.",
-      "type": "string"
-    },
-    "generatedAt": {
-      "type": "string"
-    },
-    "status": {
-      "enum": [
-        "nominal",
-        "degraded",
-        "insufficient_data"
-      ],
-      "type": "string"
-    },
-    "version": {
-      "type": "string"
-    },
-    "windows": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "avgLatencyMs": {
-            "type": "number"
-          },
-          "errorRate": {
-            "type": "number"
-          },
-          "p50LatencyMs": {
-            "type": "number"
-          },
-          "p95LatencyMs": {
-            "type": "number"
-          },
-          "p99LatencyMs": {
-            "type": "number"
-          },
-          "toolBreakdown": {
-            "additionalProperties": true,
-            "type": "object"
-          },
-          "topErrors": {
-            "items": {
-              "additionalProperties": true,
-              "properties": {
-                "count": {
-                  "type": "number"
-                },
-                "errorCode": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "totalRequests": {
-            "type": "number"
-          },
-          "windowHours": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null

Changedstore_memory1 field changed

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

13 tool updatesAug 5, 2026

Changedhealth_check1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "cacheAgeMs": {
+      "type": "number"
+    },
+    "cacheHit": {
+      "type": "boolean"
+    },
+    "capabilities": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "database": {
+      "type": "string"
+    },
+    "dbRealLatencyMs": {
+      "type": "number"
+    },
+    "engine": {
+      "type": "string"
+    },
+    "latencyMs": {
+      "type": "number"
+    },
+    "probeThresholds": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "healthy",
+        "degraded",
+        "unhealthy"
+      ],
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "version"
+  ],
+  "type": "object"
+}

Changedinitialize_context1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "error": {
+      "description": "Present only on fail-closed path.",
+      "type": "string"
+    },
+    "initialized": {
+      "type": "boolean"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "initialized",
+    "count",
+    "memories"
+  ],
+  "type": "object"
+}

Changedlist_memories1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "limit_applied": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "createdAt": {
+            "description": "ISO-8601 timestamp.",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "description": "Abstract summary — never plaintext content.",
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "redacted": {
+      "type": "boolean"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

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

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

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

Changedrecall1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "fallback": {
+      "type": "boolean"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent": {
+            "type": "string"
+          },
+          "confidence": {
+            "enum": [
+              "high",
+              "medium_fts",
+              "low"
+            ],
+            "type": "string"
+          },
+          "content": {
+            "description": "Memory content (truncated to 300 chars in recall).",
+            "type": "string"
+          },
+          "hybridScore": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "intent": {
+            "type": "string"
+          },
+          "is_critical": {
+            "type": "boolean"
+          },
+          "memory_type": {
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "ISO-8601 timestamp.",
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "queryCacheHit": {
+      "type": "boolean"
+    },
+    "recallLatencyMs": {
+      "type": "number"
+    },
+    "recall_mode": {
+      "type": "string"
+    },
+    "redacted": {
+      "type": "boolean"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    },
+    "sessionCacheHit": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

Changedrecall_memory1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "fallback": {
+      "type": "boolean"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent": {
+            "type": "string"
+          },
+          "confidence": {
+            "enum": [
+              "high",
+              "medium_fts",
+              "low"
+            ],
+            "type": "string"
+          },
+          "content": {
+            "description": "Memory content (truncated to 300 chars in recall).",
+            "type": "string"
+          },
+          "hybridScore": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "intent": {
+            "type": "string"
+          },
+          "is_critical": {
+            "type": "boolean"
+          },
+          "memory_type": {
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "ISO-8601 timestamp.",
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "queryCacheHit": {
+      "type": "boolean"
+    },
+    "recallLatencyMs": {
+      "type": "number"
+    },
+    "recall_mode": {
+      "type": "string"
+    },
+    "redacted": {
+      "type": "boolean"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    },
+    "sessionCacheHit": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "memories",
+    "count"
+  ],
+  "type": "object"
+}

Changedsave_memory1 field changed

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

Changedsave_to_synapse1 field changed

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

Changedsearch1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_id": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent": {
+            "type": "string"
+          },
+          "content": {
+            "type": "string"
+          },
+          "intent": {
+            "type": "string"
+          },
+          "is_critical": {
+            "type": "boolean"
+          },
+          "memory_type": {
+            "type": "string"
+          },
+          "timestamp": {
+            "type": "string"
+          },
+          "trust_quotient": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "scope_source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "results",
+    "count"
+  ],
+  "type": "object"
+}

Changedslo_report1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "description": "Error code on admin-auth failure.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only on admin-auth failure.",
+      "type": "string"
+    },
+    "generatedAt": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "nominal",
+        "degraded",
+        "insufficient_data"
+      ],
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    },
+    "windows": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "avgLatencyMs": {
+            "type": "number"
+          },
+          "errorRate": {
+            "type": "number"
+          },
+          "p50LatencyMs": {
+            "type": "number"
+          },
+          "p95LatencyMs": {
+            "type": "number"
+          },
+          "p99LatencyMs": {
+            "type": "number"
+          },
+          "toolBreakdown": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "topErrors": {
+            "items": {
+              "additionalProperties": true,
+              "properties": {
+                "count": {
+                  "type": "number"
+                },
+                "errorCode": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "totalRequests": {
+            "type": "number"
+          },
+          "windowHours": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changedstore_memory1 field changed

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

Related MCP Connectors

Cairn.ink Memory
ink.cairn
Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.
Knowledge & Memory RAG Systems
135
https://cairn.ink/api/mcp
Maximem Synap A
ai.maximem
Persistent memory for AI agents to retain, retrieve, and recall conversation context through MCP.
AI & Machine Learning Knowledge & Memory
4248
https://synap-mcp.maximem.ai/mcp
khive
ai.khive
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Knowledge & Memory Project Management
1
https://khive.ai/v1/mcp
memnode
dev.memnode
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Knowledge & Memory Autonomous Agents Agent Orchestration
2
https://api.memnode.dev/mcp

Related MCP Servers

saihm-mcp-server (standards
Autonomous Agents Knowledge & Memory
SAIHM-Admin
A
license
A
quality
A
maintenance
Sovereign, encrypted, persistent memory for AI agents. Eight MCP tools — remember, recall, forget (GDPR Art. 17 erasure), share, governance. Anchored on COTI V2 mainnet. Apache-2.0.
Updated 23 days ago (2026-10-11 07:51 UTC)
8
53 npm
2
Apache 2.0
Vivioo MCP Server
Agent Orchestration Autonomous Agents
viviooio
A
license
Not graded
quality
D
maintenance
Trust infrastructure for AI agents enabling directory browsing, agent submission/verification, job applications, and peer feedback exchange via MCP.
Updated 5 months ago (2026-05-31 15:39 UTC)
MIT
Munnin
Knowledge & Memory Autonomous Agents
alvseek
A
license
Not graded
quality
B
maintenance
Enables AI agents to maintain a persistent identity and structured memory—including reasoning patterns, episodic history, and knowledge—while exposing procedures for managing that memory over MCP.
Updated 11 days ago (2026-10-24 04:56 UTC)
Apache 2.0
SharedContext
Knowledge & Memory Autonomous Agents
Eversmile12
A
license
Not graded
quality
D
maintenance
Provides encrypted, portable memory for AI agents via MCP, allowing fact storage, conversation recall, and cross-machine sync using Arweave.
Updated 8 months ago (2026-02-24 13:54 UTC)
14 npm
50
MIT

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.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources