Skip to main content
Glama
l33tdawg

(S)AGE

by l33tdawg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

sage_remember

Store durable facts or session observations in SAGE, and correct prior memories by replacing them safely before the old record is challenged. Use it to preserve verified knowledge across sessions.

Instructions

Store a memory in SAGE. When domain is omitted, app-v23 uses this agent's approved owned home domain (older nodes retain the legacy general default); an explicit domain is never remapped. For a correction, pass replaces_memory_id here instead of calling sage_forget first: SAGE stores and verifies the replacement before it challenges the old memory, so interruption can leave both records but can never leave neither. IMPORTANT: Use type='fact' (confidence 0.95) for durable knowledge that should persist long-term and be visible across all agents — infrastructure details (IPs, hostnames, SSH commands, URLs, ports), architecture decisions, verified configurations, credentials paths, and server specs. Use type='observation' for ephemeral session context. Facts survive confidence decay and cross provider boundaries; observations do not.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoUser-defined labels for this memory (e.g. 'important', 'project-x')
typeNoMemory type. A correction inherits the original type when omitted. fact (0.95+): verified durable knowledge — IPs, hostnames, architecture decisions, configs, infrastructure. observation (0.80): session-level context — what happened, what was discussed. inference (0.60): hypotheses and conclusions. task: actionable items.observation
domainNoDomain tag. When omitted, a correction inherits its source domain and a new memory uses this app-v23 agent's owned home domain (legacy nodes use general). Explicit values are never silently remapped.
contentYesThe memory content to store
evidenceNoOptional source text this memory is based on (a quote, log line or document excerpt, up to 32 KiB). It stays on this node and never enters the chain; a node running the memory gate checks that it supports the memory as stated. Not for tasks.
confidenceNoConfidence score 0-1
replacement_reasonNoOptional audit reason recorded when the replaced memory is challenged.
replaces_memory_idNoOptional committed memory ID this content corrects. The replacement is committed first; only then is the old memory challenged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv11.23.11
    • addedInput schema / properties / evidence
      Added value: +{
+  "description": "Optional source text this memory is based on (a quote, log line or document excerpt, up to 32 KiB). It stays on this node and never enters the chain; a node running the memory gate checks that it supports the memory as stated. Not for tasks.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv11.16.2
    • removedInput schema / properties / domain / default
      Removed value: -"general"
    • changedInput schema / properties / domain / description
      Previous value: -"Domain tag (e.g. general, security, code). A correction inherits the original domain when omitted."New value: +"Domain tag. When omitted, a correction inherits its source domain and a new memory uses this app-v23 agent's owned home domain (legacy nodes use general). Explicit values are never silently remapped."
  3. Addedv11.14.2
  4. Removedv11.13.8
  5. Addedv11.13.0
  6. Removedv11.9.2
  7. Addedv8.1.0
  8. Removedv8.0.0
  9. Addedv7.6.1
  10. Removedv7.5.9
  11. Changed1 schema field changedv6.6.9
    • addedInput schema / properties / type / description
      Added value: +"Memory type. fact (0.95+): verified durable knowledge — IPs, hostnames, architecture decisions, configs, infrastructure. observation (0.80): session-level context — what happened, what was discussed. inference (0.60): hypotheses and conclusions. task: actionable items."
  12. First observedv4.5.2

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so: it discloses the domain default/remap rule, the write-ordering guarantee (replacement committed and verified before the old memory is challenged, so interruption can leave both but never neither), and the durability semantics of facts vs observations. The evidence-field note (stays on node, never enters the chain) adds auth/scope context an agent could not infer.

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?

Front-loaded with the core action, then the correction workflow, then the type guidance marked IMPORTANT — a sensible priority order. It is dense rather than wasteful, though the type/domain semantics are restated from the schema and could be trimmed slightly.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers creation, correction, defaulting, and durability. The remaining gap is that it never says how the agent obtains the committed memory ID that replaces_memory_id expects, which matters for the correction workflow it promotes.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the cross-agent visibility and decay behavior tied to type='fact' vs 'observation', and states the omission semantics for domain and replacement type inheritance. It stops short of full compensation only because the critical ordering guarantee for replaces_memory_id is largely mirrored in the schema field text.

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?

Opens with a specific verb+resource ('Store a memory in SAGE') and immediately differentiates itself from siblings by covering the correction path (replaces_memory_id vs sage_forget) and the type taxonomy. An agent can tell this apart from sage_forget, sage_recall, and sage_link without opening a schema.

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

Usage Guidelines5/5

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

Explicitly states when to use type='fact' (durable, cross-agent, survives decay) versus type='observation' (ephemeral session context), and explicitly says to pass replaces_memory_id 'instead of calling sage_forget first.' Names both the alternative and the selecting condition.

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

Deploy Server

Other Tools