Skip to main content
Glama

Batch Encode Memories

batch_encode

Encode multiple memories atomically in one call, so related long-term memories are stored together without partial writes.

Instructions

Encode multiple memories atomically in a single batch call.

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": {
      "memories": "<memories>"
    },
    "name": "batch_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoriesYesArray of memory objects to encode.
namespaceNoDefault namespace for memories in the batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The word 'atomically' is a genuine behavioral disclosure beyond the annotations: it tells the agent the whole batch succeeds or fails as a unit, which matters materially for a non-idempotent, non-readOnly write. Annotations already cover the safety profile (destructiveHint=false, openWorldHint=false), so this added semantic is the right kind of contribution.

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?

A single tight sentence with the operation, scope, and key semantic front-loaded. No filler and nothing to trim.

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 write tool with no output schema, the description covers atomicity but omits what happens on partial failure (e.g., error reporting), any batch size limits, and duplicate/dedup behavior. Adequate given the rich schema and annotations, but not complete for a batch mutation.

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%, including the 'Default namespace for memories in the batch' description, so the schema already carries parameter meaning. The description adds nothing about per-item fields (type, salience, context) or how the top-level namespace interacts with per-item namespaces.

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?

Names a specific verb and resource plus scale and semantics: 'Encode multiple memories atomically in a single batch call.' The plural/batch framing implicitly distinguishes it from the singular encode_memory sibling, but it never names that alternative explicitly.

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: the agent can infer this is for encoding more than one memory at a time rather than making repeated encode_memory calls. There is no explicit when-to-use/when-not guidance, no mention of batch size limits, and no named alternative.

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