Skip to main content
Glama
yamantaka520

agent-memory-os

memory_recall_feedback

Report whether recalled memories were helpful to tune future ranking. Strengthen helpful memories and links, or weaken misleading ones to improve recall relevance.

Instructions

Report whether recalled memories were helpful, to tune future ranking.

    This closes the learning loop: `helpful=True` strengthens the memories and the
    links between them (they will resurface more readily); `helpful=False` weakens
    them and lowers their confidence. Only memories visible to this agent are
    affected — you cannot influence another identity's memories. Returns a summary
    of what was reinforced or weakened.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
helpfulNoTrue if the recalled memories helped (reinforce them); False if they misled you (weaken them and lower confidence).
memory_idsYesIds of memories that were just recalled together, whose usefulness you are reporting.
create_colinksNoIf true, create weak 'co_recalled' links between the given memories that weren't already linked.
Behavior4/5

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

With no annotations, the description carries the full burden. It transparently explains the behavioral effects: strengthening/weakening memories and links, and lowering confidence for negative feedback. It also mentions that a summary is returned, providing insight into the tool's output.

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 concise and well-structured, with no wasted words. It front-loads the core purpose and follows with necessary behavioral details and limitations in a clear, organized manner.

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 a tool with 3 parameters and no output schema, the description provides sufficient context: purpose, effects, scope, and return value. It could optionally include an example, but the current level is adequate for correct tool selection and use.

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%, providing baseline of 3. The description adds value by explaining the semantic meaning of each parameter: 'helpful' controls reinforcement vs. weakening, 'memory_ids' specifies which memories are being evaluated, and 'create_colinks' adds co-recalled links. This goes beyond the schema descriptions.

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 clearly states the tool's purpose: to report whether recalled memories were helpful. It uses a specific verb ('Report') and resource ('recalled memories'), and distinguishes this tool from sibling tools like memory_search or memory_add by explaining its role in the learning loop.

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 provides clear context on when to use the tool (after recalling memories) and explains the consequences of 'helpful=True/False'. It also notes the limitation that only the agent's own memories are affected, offering guidance on proper usage.

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/yamantaka520/Agent-Memory-OS'

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