Skip to main content
Glama
CodeAbra

iai-personal-memory-engine

by CodeAbra
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

memory_contradict

Correct a stored fact by marking the original record as contradicted and saving the updated fact as a new linked record, preserving history.

Instructions

Mark a record contradicted; new fact stored as a NEW record (old NEVER deleted). Mutates store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID of the record being contradicted.
new_factYesThe updated verbatim fact. Stored as a new record; the old record is preserved (episodic write-once) and linked via a `contradicts` edge.
cue_embeddingNoOptional pre-computed embedding vector for the contradicting fact (EMBED_DIM=384 floats; bge-small-en-v1.5). When omitted, the daemon embeds new_fact server-side.
epistemic_statusNoCaller-declared epistemic status of the corrected fact. Omit for 'unknown' (default, no behavior change). A value outside the enum is coerced to 'unknown' server-side, never rejected.unknown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tsNo
edge_typeNo
original_idNo
new_record_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / epistemic_status
      Added value: +{
+  "default": "unknown",
+  "description": "Caller-declared epistemic status of the corrected fact. Omit for 'unknown' (default, no behavior change). A value outside the enum is coerced to 'unknown' server-side, never rejected.",
+  "enum": [
+    "fact",
+    "estimate",
+    "hypothesis",
+    "opinion",
+    "unknown"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / cue_embedding / description
      Previous value: -"Optional pre-computed embedding vector for the contradicting fact (its dimension must match the current store). When omitted, the daemon embeds new_fact server-side."New value: +"Optional pre-computed embedding vector for the contradicting fact (EMBED_DIM=384 floats; bge-small-en-v1.5). When omitted, the daemon embeds new_fact server-side."
  3. Changed1 schema field changedv2.3.1
    • changedInput schema / properties / cue_embedding / description
      Previous value: -"Optional pre-computed embedding vector for the contradicting fact (EMBED_DIM=384 floats; bge-small-en-v1.5). When omitted, the daemon embeds new_fact server-side."New value: +"Optional pre-computed embedding vector for the contradicting fact (its dimension must match the current store). When omitted, the daemon embeds new_fact server-side."
  4. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / new_fact / description
      Previous value: -"The updated verbatim fact. Stored as a new record."New value: +"The updated verbatim fact. Stored as a new record; the old record is preserved (episodic write-once) and linked via a `contradicts` edge."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "edge_type": {
+      "type": "string"
+    },
+    "new_record_id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "original_id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "ts": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already show this is a mutating, non-destructive operation. The description adds valuable behavioral clarity by explicitly stating that the old record is NEVER deleted and that the store is mutated. This goes beyond the raw annotation flags and sets correct expectations about data preservation.

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 a single front-loaded sentence that immediately states the action, the key side effect, and the safety guarantee. Every clause earns its place; there is no redundant or vague filler.

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?

Given the rich input schema, annotations, and presence of an output schema, this description is sufficient. It covers the essential behavioral contract—mutation, preservation of old records, and creation of a new contradicted record—without needing to restate schema details.

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

Parameters3/5

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

Schema description coverage is 100%, and each parameter including id, new_fact, cue_embedding, and epistemic_status already has a detailed schema description. The tool description contributes no additional parameter-level nuance, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: 'Mark a record contradicted' and clearly states the core effect—new fact stored as a NEW record while the old is never deleted. This differentiates the tool from siblings like memory_capture or memory_reinforce without needing to name them.

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

Usage Guidelines3/5

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

The description implies the usage—contradicting a record while preserving the old fact—but gives no explicit guidance about when to prefer this over memory_capture, memory_reinforce, or other alternatives. There are no stated exclusions or conditional routing cues.

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/CodeAbra/iai-personal-memory-engine'

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