Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_memory_write

Store memory entries in the local cortex knowledge base with optional tags, source, and summary so coding agents can recall information later.

Instructions

Write a memory entry to the cortex knowledge base for persistent storage

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "cortex_memory_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tags for the memory
sourceNoOptional source identifier
contentYesThe memory content to store
summaryNoOptional summary, auto-generated if empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Persistent storage' hints at durability, but nothing is said about overwrite semantics, duplicate handling, required permissions, whether the write is idempotent, or what identifier is returned for later retrieval or deletion.

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?

A single front-loaded sentence with no filler; the verb and resource lead. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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

Completeness3/5

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

For a simple one-required-parameter write with fully documented params and no output schema, the description is minimally adequate. With zero annotation coverage, however, an agent still lacks the mutation semantics — dedup, overwrite, permissions — needed to call it confidently.

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 100% and every parameter (content, tags, source, summary) is documented inline, so the baseline is 3. The description adds no extra meaning about how tags are matched on search or how summary auto-generation is triggered beyond what the schema already says.

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?

States a specific verb ('Write') and resource ('a memory entry') plus the destination ('cortex knowledge base'), and the singular article implicitly separates it from cortex_memory_batch. It does not explicitly name any sibling, but the action and target are unmistakable.

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?

Usage is only implied by the phrase 'persistent storage' – an agent can infer this is for durable retention rather than transient scratch data. There is no explicit when-to-use, no mention of when a batch write or search-first dedup check would be preferable, and no prerequisites.

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