Plain Text Memory MCP

Overview Schema Source Related Servers Discussions Admin

Edit observation

edit_observation

DestructiveIdempotent

Replace one observation's exact text in a memory entity to correct or update a stored fact, preserving original metadata and recording who edited it and when.

Instructions

Replace one observation's text in place.

Keeps the observation's original added_at and agent, and records the edit in edited_at and edited_by. Returns the edited observation. Fails without saving when the entity or old text does not exist, or when the entity already has the new text. To add a new fact, see add_observations.

Input Schema

TableJSON Schema

Name	Required	Description
`newText`	Yes	Replacement text, one plain sentence.
`oldText`	Yes	Exact current text of the observation.
`entityName`	Yes	Name of the entity that has the fact.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	Yes
`entityName`	Yes
`observation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare a destructive, idempotent write, and the description goes well beyond them: it preserves original added_at/agent, records edited_at/edited_by, returns the edited observation, and enumerates three no-save failure conditions. This is exactly the behavioral context an agent needs before mutating data.

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?

The core action and the alternative tool are front-loaded, and the atomic-failure clause is a genuinely useful single sentence. The unusual line-wrapping is cosmetic, though the failure sentence is slightly dense.

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?

For a 3-parameter mutation with annotations and an output schema, nothing material is missing: the agent knows what is replaced, what is preserved, what is returned, how failure manifests, and where to go for a different operation.

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% so the baseline is 3, but the description adds real semantic value: oldText must match the exact current text and the call fails without saving if it does not exist or the new text already exists. That ties parameter values directly to observable outcomes.

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?

States a precise verb+resource+scope: 'Replace one observation's text in place.' It is clearly distinguishable from sibling add_observations, which it explicitly names, and from delete_observations by virtue of being an in-place edit.

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?

Routes the agent to add_observations for adding new facts and spells out the failure conditions (entity missing, old text missing, new text already present). It does not discuss alternatives like delete_observations plus add_observations for multi-fact changes, so it is clear context rather than full when/when-not guidance.

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

Deploy Server