Skip to main content
Glama
donggyun112

keymem

by donggyun112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

correct

Update outdated memory entries with revised details, preserving the old version. Use when facts change or user provides new information.

Instructions

Update outdated information. Use when user corrects you or info changes (e.g. moved cities, changed job). Old version is preserved but weakened — never lost. Omit keys to keep the same search terms. Omit decay_profile and ttl_seconds to preserve the predecessor's policies; provide either to replace that policy. related_to links the updated memory to other memory IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysNo
sourceNo
contentYes
key_typesNo
memory_idYes
related_toNo
ttl_secondsNo
decay_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.29.0
    • addedInput schema / properties / decay_profile
      Added value: +{
+  "enum": [
+    "transient",
+    "standard",
+    "stable",
+    "permanent"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / ttl_seconds
      Added value: +{
+  "type": "number"
+}
  2. First observedv0.14.8

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers meaningful behavior: the old version is 'preserved but weakened — never lost,' establishes a non-destructive update pattern, and explains the defaulting semantics of omitted fields. It omits return format and any auth/permission behavior, but the core mutation semantics are well disclosed.

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 description is dense and front-loaded, leading with purpose then immediately covering behavior and parameter defaults in tight sentences. Every clause carries information, though it reads as a run-on paragraph rather than separated concerns.

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 an 8-parameter mutation tool with no annotations or output schema, it covers the essential behaviors (predecessor preservation, field defaults) an agent needs. Gaps remain around the undocumented source/key_types params and the response shape, but the critical decision-relevant behavior is present.

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 0% across 8 parameters, so the description must compensate. It explains the non-obvious semantics of keys, decay_profile, ttl_seconds, and related_to, but leaves source, key_types, content, and memory_id undocumented, so roughly half the parameters remain unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Update outdated information') and the examples ('moved cities, changed job') make the corrective-update intent concrete. It does not, however, explicitly differentiate itself from siblings like remember/confirm_memory, leaving that distinction to the reader.

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?

It states a clear trigger condition ('Use when user corrects you or info changes') with illustrative examples, which is solid context for selection. It stops short of naming when-not-to-use or the alternative tools (e.g. remember for new facts, forget for removal).

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

Deploy Server

Other Tools