Skip to main content
Glama

ck_memory_record

Write governed memory records to persist knowledge across sessions. Supports structured records with types like decision, finding, proof, goal, and brief for future retrieval.

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.
memoryYes
metadataNo
project_rootNoAbsolute path to the project root directory on the local filesystem.
record_typeNoRecord type classification.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
source_idNoUnique identifier of the source system or record.
source_typeNoOrigin category of the record (e.g., developer, tool_output, human_review).
summaryNoBrief human-readable summary of the record.
tagsNo
task_idNoTask identifier within the session for scoped operations.
titleNoHuman-readable title for display and search.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses idempotency and that it's a write operation, but lacks details on permissions, side effects, or rate limits. Adequate but not exhaustive.

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 fairly long but well-structured with key information upfront. Each sentence serves a purpose, though minor trimming could be done without losing value.

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?

Given the tool's complexity (12 params, nested objects) and lack of output schema, the description covers the essential aspects: idempotency, parameter formats, record types, and sibling differentiation. Missing error/return info but not critical for this tool.

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 75% (high), so baseline is 3. Description adds value by explaining record_type meanings and tags flexibility, but some parameters (e.g., metadata, session_id) are not elaborated beyond 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 'Write a governed memory record' with a specific verb and resource, and distinguishes it from siblings by naming alternative tools (ck_finding, ck_goal) for different 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?

Explicitly tells when to use this tool vs. alternatives, and provides guidance on parameter usage (plain string vs. structured object, record_type values). No exclusions mentioned but context is sufficient.

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