Skip to main content
Glama

ck_memory_record

Persist governed memory records so future agents can retrieve them via search, supporting structured notes with titles, summaries, types, and tags.

Instructions

Write a governed memory record so future agents can explicitly retrieve it via ck_memory_search. Write operation — persists to the database. Idempotent: re-submitting the same source_id updates the existing record rather than duplicating it. Pass memory as a plain string for quick notes, or as an object with body, title, summary, record_type, and tags for structured records. record_type controls retrieval filtering: use decision for architectural choices, finding for issues, proof for evidence, goal for intent, brief for task context. tags is a string or array of strings for categorization. source_id links the record to an external artifact (e.g., a review ID or commit SHA). Use ck_memory_record to persist knowledge that should survive session boundaries. Use ck_finding for policy violations with a ruling decision. Use ck_goal for durable multi-session intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoFull content body with detailed information.
tagsNo
titleNoHuman-readable title for display and search.
memoryYes
summaryNoBrief human-readable summary of the record.
task_idNoTask identifier within the session for scoped operations.
metadataNo
source_idNoUnique identifier of the source system or record.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
record_typeNoRecord type classification.
source_typeNoOrigin category of the record (e.g., developer, tool_output, human_review).
project_rootNoAbsolute path to the project root directory on the local filesystem.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
task_idNo
recordedNo
memory_idNo
session_idNo
record_typeNo
Behavior5/5

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

Discloses idempotency behavior (re-submitting same source_id updates rather than duplicates) and write operation, adding context beyond annotations. No contradiction with annotations except idempotentHint discrepancy.

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?

Front-loaded with core purpose. All sentences are informative without redundancy. Slightly long but justified due to number of parameters.

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?

Covers key parameters (memory, record_type, source_id, tags) but not all 12 parameters (e.g., task_id, session_id, project_root). However, schema descriptions fill some gaps. Adequate for complexity.

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?

Adds meaning by explaining memory parameter can be plain string or object with body, title, summary, etc. Also explains record_type enum values. Schema coverage is 75%, so description compensates moderately.

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 'Write a governed memory record' and explains persistence to database. It distinguishes from sibling tools like ck_memory_search (retrieval) and references ck_finding and ck_goal for alternative use cases.

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

Usage Guidelines5/5

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

Explicit guidance: 'Use ck_memory_record to persist knowledge that should survive session boundaries.' Also tells when to use alternatives: 'Use ck_finding for policy violations... Use ck_goal for durable multi-session intent.'

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/aryaminus/controlkeel'

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