Skip to main content
Glama

invalidate_memory

Mark a memory as incorrect or outdated to reduce its trust score and rank lower in recall, ensuring accuracy of retrieved information.

Instructions

Mark a memory as incorrect or outdated.

Decreases the memory's trust score and records the reason in the trust history. Use this when you discover that a recalled memory contains inaccurate or outdated information.

Reasons and their default penalties:

  • outdated: -0.10 (information is stale but was once correct)

  • partially_incorrect: -0.15 (some details are wrong)

  • factually_wrong: -0.30 (fundamentally incorrect)

  • superseded: -0.05 (replaced by newer information)

  • low_utility: -0.05 (not useful in practice)

Trust score is floored at 0.0. Memories with very low trust will rank lower in recall results due to trust-weighted scoring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional note explaining the invalidation context
reasonNoReason for invalidation: 'outdated' (info is stale), 'partially_incorrect' (some details wrong), 'factually_wrong' (fundamentally incorrect), 'superseded' (replaced by newer info), 'low_utility' (not useful). If not specified, uses default penalty.
penaltyNoCustom trust penalty (overrides reason default). If None, uses reason's default.
memory_idYesID of memory found to be incorrect/outdated

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses trust score decrease, recording reason in history, default penalties per reason, floor at 0.0, and effect on recall rankings. No annotations present, so description fully covers behavioral details.

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?

Concise and front-loaded with main purpose. Bullet list adds structure but could be slightly more streamlined; still no unnecessary 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?

Covers all aspects: purpose, when to use, behavior, parameters, trust mechanism. Output schema exists so return values are already defined. No missing details.

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% with descriptions. Description adds value by detailing reason penalties and overriding behavior beyond schema, but schema already explains each parameter adequately.

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 'Mark a memory as incorrect or outdated,' using a specific verb and resource. It distinguishes from sibling tools like 'forget' by focusing on invalidation rather than deletion.

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?

Explicitly says 'Use this when you discover that a recalled memory contains inaccurate or outdated information.' Does not mention when not to use, but the context is clear enough.

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/michael-denyer/memory-mcp'

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