Skip to main content
Glama
ArkaAiAdmin

Agentic Memory

by ArkaAiAdmin

memory_note

Read, update, delete, patch, supersede, or revert a memory note while capturing the rationale for each action to maintain an audit trail.

Instructions

CRUD operations on a specific memory note.

Sprint 2 additions: patch, revert_supersede actions + rationale capture.

Args: note_id: The note ID (e.g. "lessons/my-note"). action: "read" | "update" | "delete" | "restore" | "supersede" | "patch" | "revert_supersede". content: New content (required for update). category: New category (for update). title_slug: New slug (for update/supersede target). tags: New tags (for update). rationale: Reason for the action (required for supersede, patch, revert_supersede; recommended for delete). additions: Text segments to insert (for patch action). deletions: Text segments to remove by content match (for patch action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
actionNoread
contentNo
note_idYes
categoryNo
additionsNo
deletionsNo
rationaleNo
title_slugNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It lists actions and parameters but does not disclose side effects, idempotency, permissions, or what happens on supersede (e.g., versioning). Minimal behavioral insight beyond action enumeration.

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 front-loaded with the purpose, then lists actions and parameters. It includes meta notes (Sprint 2) which add context but could be more streamlined. Generally efficient with minimal redundancy.

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 a complex tool with 9 parameters and multiple actions, the description covers all actions and required parameters. Output schema exists so return value explanation is unnecessary. Lacks some context on constraints (e.g., max length) but is largely complete.

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?

Schema coverage is 0%, meaning parameters lack schema descriptions. The description compensates fully by explaining each parameter's purpose (e.g., note_id format, additions/deletions for patch). Adds significant value beyond the raw schema.

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 it performs CRUD operations on a specific memory note, listing multiple actions like read, update, delete, etc. It is specific and distinguishes from siblings that operate on collections or other aspects.

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 provides per-action parameter requirements (e.g., rationale for supersede) but does not explicitly compare to sibling tools or specify when to avoid using this tool. Usage context is implied but not fully elucidated.

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/ArkaAiAdmin/Agentic-Memory'

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