Skip to main content
Glama

Gnosem

by dev.gnosem

memory_write_bulk

Write up to 50 memories in a single call. Each entry runs the same path as memory_write (semantic dedup by default; pass force:true per-entry to skip). Embeddings + optimizations run in parallel; D1 inserts are batched. Returns { results: [...] } with one entry per input in the same order — each is { id, created_at, optimized? } on success, { id, created_at, deduped, matched_score } on dedup, or { error } on failure. Free-tier limits apply to the sum: if adding N would exceed 200, the first (200 - existing) succeed and the rest return an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoriesYesArray of memory-write entries (1–50).

TDQS

A4.6/5.0
Behavior5/5

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

Despite no annotations, the description is highly transparent: it details parallel embeddings, batched D1 inserts, return format for success/dedup/error, and free-tier limit handling. No contradictions exist.

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 a single paragraph that efficiently conveys key information. While it could be broken into sections for readability, it is front-loaded with the core action and avoids unnecessary repetition.

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

Completeness5/5

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

Given the lack of an output schema, the description thoroughly explains the return format and handles edge cases (dedup, failure, free-tier limit). All important aspects are covered.

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?

Schema coverage is 100% with descriptions for each field. The description adds value by explaining dedup behavior, parallel execution, and return structure, going beyond the schema to provide operational context.

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 that this tool writes up to 50 memories in a single call, using the same path as memory_write. This distinguishes it from the sibling tool memory_write, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description explains that it runs the same path as memory_write, includes dedup behavior and force option, and discusses free-tier limits. However, it does not explicitly state when to choose this bulk version over the single memory_write, relying on the name and context to imply bulk scenarios.

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

All Gnosem toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: write (single/bulk), search, list, forget, supersede. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'memory_' prefix and verb pattern, using snake_case throughout. Naming is predictable and clear.

Tool Count5/5

6 tools is well-scoped for a memory management server, covering essential operations without being excessive or insufficient.

Completeness4/5

Covers write (single/bulk), search, list, soft-delete, and supersede. Minor gap: no direct single-item retrieval by ID, but search can serve that purpose.

Resources