Skip to main content
Glama

correct

Destructive

Update an outdated or incorrect memory by replacing it with a corrected version, preserving history and entity relationships.

Instructions

Correct an existing memory — tombstones the old one and creates a corrected version.

WHEN TO USE: When the user corrects a recalled fact.

  • "Actually, we're using Python 3.12, not 3.11" → correct the memory. Preserves history and transfers entity relationships to the new memory.

Args: rid: The memory ID to correct. new_text: The corrected text content. new_importance: Optional updated importance (0.0-1.0). new_valence: Optional updated valence (-1.0 to 1.0). correction_note: Why the correction was made.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ridYes
new_textYes
new_valenceNo
new_importanceNo
correction_noteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate destructiveHint=true, and the description adds details about tombstoning, preserving history, and transferring entity relationships, which goes beyond the annotations to inform the agent of the tool's side effects.

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: a one-line purpose, a usage guideline example, and a clear list of arguments. No superfluous text.

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 tool's complexity (5 params, destructive action, output schema exists), the description covers purpose, usage, parameter semantics, and behavioral effects, making it self-sufficient for an agent.

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?

Despite 0% schema description coverage, the description provides meaningful explanations for each parameter (e.g., 'rid: The memory ID to correct'), adding clarity and reducing ambiguity for invocation.

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 verb 'correct' and the resource 'memory,' and explains the mechanism (tombstones old, creates corrected version). It distinguishes from siblings like 'forget' and 'remember' by specifying it is for corrections.

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?

Includes a 'WHEN TO USE' section with a clear example for user corrections. However, it does not explicitly state when not to use or list alternative tools, leaving room for ambiguity in edge cases.

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/yantrikos/yantrikdb-mcp'

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