Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_memory_batch

Store up to 50 memory entries in one call to save a batch of facts at the end of a session. Use it to capture session insights without writing each memory separately.

Instructions

Write multiple memory entries in a single call (max 50), for storing a batch of facts at the end of a session.

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": {
      "items": "<items>"
    },
    "name": "cortex_memory_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesMemory entries to write in one call (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the batch cap of 50 and the intended moment of use, but says nothing about failure semantics (partial vs atomic writes), duplicate handling, or overwrite behavior for an operation that mutates stored memory.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and resource, then the constraint, then the use case. No redundant or filler wording.

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 one-parameter batch write with full schema coverage and no output schema, the description covers purpose, capacity limit, and intended usage. Only the mutation-safety details (atomicity, duplicates) are absent, which is a modest gap rather than a blocking one.

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?

With 100% schema description coverage and a single 'items' parameter already documented as 'Memory entries to write in one call (max 50)', the schema does the heavy lifting. The description only restates the max-50 limit and adds no nested field guidance beyond what the schema provides.

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 and resource ('Write multiple memory entries') plus a scope limit ('max 50'), which distinguishes it from a single-entry write and from the delete/search siblings by implication. It does not name the single-write sibling explicitly, so the differentiation is inferred rather than stated.

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 phrase 'for storing a batch of facts at the end of a session' gives a real usage context and timing cue. However, it never names an alternative (e.g., cortex_memory_write for single facts) or states when not to use a batch, leaving the choice to inference.

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