Skip to main content
Glama
0Mattias

bettermemory

by 0Mattias
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

episode_promote

Promote a journal episode into a durable memory for long-term reuse. Routes through memory_write's dedup and scope checks, and deletes the source episode after successful commit.

Instructions

Promote a journal entry (episode) into a durable memory. Routes through memory_write — the durability gate, scope-mismatch detection, dedup, and user-inference confirmation flow all apply.

Use this when an iteration's takeaway turns out to be a fact worth keeping across sessions, not just a run-state note.

Loop/working state belongs in episodes; session close is when to promote the takeaways that hardened.

On successful commit the source episode is deleted (its content has been distilled). On pending (user-inference category), the source episode is held for memory_write_confirm to delete — memory_write_cancel keeps the episode so you can retry. On any other non-committed status (duplicate, previously_removed, transient_warning, scope_mismatch, ungrounded) the source episode is left untouched so you can adjust and re-promote.

Body default: when use_body=False (default), the durable memory's body is the episode's takeaway. Set use_body=True to use the full episode body. An episode with no takeaway requires use_body=True.

Returns the memory_write response shape with one extra field: promoted_from_episode_id: str so the caller can correlate the promotion attempt back to its source episode regardless of outcome (committed / pending / duplicate / scope_mismatch / etc.).

Parameters:

  • episode_id: ULID of the source episode.

  • scopes: scopes for the durable memory. Required.

  • category (default 'fact'): memory category. user-inference still requires explicit user confirmation.

  • confidence (default 'medium'), source (default 'explicit-statement'): standard memory_write fields.

  • use_body=False: when True, use the episode's body instead of its takeaway.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopesYes
sourceNoexplicit-statement
categoryNofact
use_bodyNo
confidenceNomedium
episode_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A5/5.0
Behavior5/5

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

Discloses critical side effects: successful commit deletes the source episode; pending holds it for memory_write_confirm; other non-committed statuses leave it untouched. Also explains body default behavior and return shape, which goes well beyond the absence of 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?

The description is organized in clear paragraphs and a parameter list, with every sentence delivering necessary detail. No fluff or repetition; it is appropriately sized for a tool with complex side effects and routing.

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?

Despite no annotations, the description covers all important operational contexts: routing through memory_write, all possible statuses and their effects, body default logic, and the output shape. The presence of an output schema reduces the need to explain return types, but the description still adds the extra promoted_from_episode_id field.

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

Parameters5/5

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

Although the schema has no property descriptions, the description compensates fully by explaining each parameter: episode_id is a ULID, scopes required, category default 'fact', confidence/source standard fields, and use_body behavior. This adds significant meaning beyond the bare schema.

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 opens with 'Promote a journal entry (episode) into a durable memory,' which uses a specific verb and resource. It further clarifies the relationship to memory_write, distinguishing this tool from sibling tools like episode_write or memory_search.

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 'Use this when an iteration's takeaway turns out to be a fact worth keeping across sessions' and contrasts with 'Loop/working state belongs in episodes.' This provides clear when-to-use guidance and implies alternatives like episode_write for transient state.

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/0Mattias/bettermemory'

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