Skip to main content
Glama
zzhang82

Agent Memory Bridge

store

Store compact memory records or coordination signals to a bridge for later retrieval and workflow handoffs.

Instructions

Store one entry in the bridge for later retrieval or coordination.

Use this tool when you want to persist a compact memory record or write a signal that another workflow can poll later. Write durable knowledge as kind="memory" and transient coordination events as kind="signal".

Returns the stored entry identifier, timestamp, and duplicate information. Repeated memory writes may deduplicate; signal writes are intended to remain append-like.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceYesLogical memory bucket to write into, such as `project:<workspace>`, `domain:<name>`, or `global`.
contentYesMachine-readable memory payload to persist. Prefer compact claims, fixes, decisions, or signals over long transcript-style prose.
kindNo`memory` stores durable knowledge for later retrieval. `signal` stores pollable coordination events for handoff or workflow triggers.memory
tagsNoOptional stable labels for retrieval and filtering, for example `kind:gotcha`, `domain:retrieval`, or `project:demo-app`.
session_idNoOptional session or thread identifier used to trace entries back to one conversation or work unit.
actorNoOptional writer identity such as an agent, reviewer, or user profile.
titleNoOptional short label for UI display or scanning. Keep it concise and stable when possible.
correlation_idNoOptional shared identifier used to link related writes, handoffs, or workflow events across entries.
source_appNoOptional source name for the writer, such as `codex`, `codex-session-watcher`, or another local automation.
source_clientNoOptional external client identifier such as `codex`, `antigravity`, or `claude-code`.
source_modelNoOptional external model identifier such as `gpt-5.4` or `gemini-2.5-pro`.
client_session_idNoOptional external client session or thread identifier when the caller can provide one.
client_workspaceNoOptional external client workspace root or project label when useful for provenance.
client_transportNoOptional transport label such as `stdio`, `http`, or `sse`.
expires_atNoOptional ISO-8601 expiry timestamp for a signal. Use this when a coordination event should stop being claimable after a deadline.
ttl_secondsNoOptional relative expiry in seconds for a signal. Useful for short-lived handoff or review events.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses return value (identifier, timestamp, duplicate info) and deduplication behavior: 'Repeated memory writes may deduplicate; signal writes are intended to remain append-like.' This is sufficient for an agent to understand the behavioral traits.

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 very concise, with two focused paragraphs. The first paragraph states the purpose and usage, the second adds behavioral details. No redundant or extraneous sentences.

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

Completeness5/5

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

Given the tool's 16 parameters and complexity, the description covers the essential behavioral aspects (kind differentiation, dedup behavior, return value). It also references sibling tools and context effectively, making it complete for an agent to select and invoke.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the semantic difference between memory and signal kinds, and by describing the return value structure, going beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Store one entry in the bridge for later retrieval or coordination.' It clearly distinguishes between the two kinds (memory and signal) and differentiates from siblings like recall (retrieval) and forget.

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

Usage Guidelines4/5

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

The description explicitly says when to use: 'Use this tool when you want to persist a compact memory record or write a signal that another workflow can poll later.' It explains the two kinds and their respective purposes, though it does not explicitly mention when not to use it or alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zzhang82/Agent-Memory-Bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server