Skip to main content
Glama

memory_encode

Persist an AI agent's memory with optional emotional affect, tags, context, and salience, enabling structured recall and consolidation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for categorization
affectNoEmotional affect - how this memory feels
sourceYesSource type of the memory
contentYesThe memory content to encode
contextNoSituational context as key-value pairs (e.g., {task: "debugging", domain: "payments"})
privateNoIf true, memory is only visible to the AI and excluded from public recall results
salienceNoImportance weight 0-1
wait_for_consolidationNoIf true, wait for post-encode validation/interference/resonance work before returning. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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