Skip to main content
Glama

Memory Update

localnest_memory_update

Update stored memory entries and append revisions to maintain accurate local knowledge bases for AI agents.

Instructions

Update a stored memory entry and append a revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
kindNoknowledge
titleNo
summaryNo
contentNo
statusNoactive
importanceNo
confidenceNo
tagsNo
linksNo
scopeNo
source_typeNo
source_refNo
change_noteNoMemory updated
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • The handler function for 'localnest_memory_update', which calls memory.updateEntry.
    async ({ id, ...patch }) => {
      const result = await memory.updateEntry(id, patch);
      return normalizeMemoryEntryPayload(result, {
        updated: true
      });
    }
  • The registration block for 'localnest_memory_update' including its input schema and metadata.
    ['localnest_memory_update'],
    {
      title: 'Memory Update',
      description: 'Update a stored memory entry and append a revision.',
      inputSchema: {
        id: z.string().min(1),
        kind: MEMORY_KIND_SCHEMA.optional(),
        title: z.string().min(1).max(400).optional(),
        summary: z.string().max(4000).optional(),
        content: z.string().min(1).max(20000).optional(),
        status: MEMORY_STATUS_SCHEMA.optional(),
        importance: z.number().int().min(0).max(100).optional(),
        confidence: z.number().min(0).max(1).optional(),
        tags: z.array(z.string()).max(50).optional(),
        links: z.array(MEMORY_LINK_SCHEMA).max(50).optional(),
        scope: MEMORY_SCOPE_SCHEMA.optional(),
        source_type: z.string().max(60).optional(),
        source_ref: z.string().max(1000).optional(),
        change_note: z.string().max(400).default('Memory updated')
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: false
      }
    },
Behavior4/5

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

The description adds valuable behavioral context by stating it 'append[s] a revision,' which explains the annotation idempotentHint=false and indicates versioning behavior. However, it fails to clarify whether omitted fields are preserved or cleared during the update, a critical omission for a mutation tool with 15 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-sentence description is efficiently worded without redundancy, but it is undersized for the tool's complexity. Given the zero schema documentation and numerous parameters, additional sentences explaining critical parameters or usage constraints would be necessary to earn a higher score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is inadequate for a tool with 15 undocumented parameters and complex nested structures. While the existence of an output schema excuses the lack of return value explanation, the description must compensate for the 0% schema coverage by detailing update semantics, required identifiers, and field handling—none of which are provided.

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

Parameters2/5

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

With 0% schema description coverage across 15 complex parameters (including nested objects like 'scope' and 'links'), the description fails to compensate by explaining key parameters. While 'stored memory entry' implies the 'id' parameter is required, the description provides no guidance on other fields like 'change_note' (likely related to the revision) or partial update behavior.

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 clearly states the tool updates a 'stored memory entry' and specifically mentions appending a revision—a key distinguishing feature from simple overwrites. However, it does not explicitly differentiate when to use this versus the sibling 'localnest_memory_store' tool for creating new entries.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the numerous sibling memory tools (such as store, capture_event, or delete). There are no stated prerequisites, conditions, or exclusions to help an agent select the correct tool for a given scenario.

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/wmt-mobile/localnest'

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