Memanto MCP

batch_remember

Persist up to 100 independent memories in a single request, ideal for batch-saving extracted facts or structured data from documents.

Instructions

Store many memories at once (up to 100). Use this when you have a list of independent facts to persist - e.g. extracting structured data from a document. For a single item, prefer remember.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	No	Memanto agent identifier the memory belongs to (required: no MEMANTO_DEFAULT_AGENT_ID is configured).
`memories`	Yes	List of memory dicts. Each item supports the same fields as `remember` (content [required], type, title, confidence, tags, source, provenance) with the same allowed values; an item without a source is attributed to the calling client. Max 100 items.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`failed`	No
`status`	Yes
`message`	No
`results`	No
`agent_id`	Yes
`namespace`	No
`successful`	No
`total_submitted`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.8Aug 5, 2026

changedInput schema / properties / memories / description

Previous value: -"List of memory dicts. Each item supports the same fields as `remember` (content [required], type, title, confidence, tags, source, provenance). Max 100 items."New value: +"List of memory dicts. Each item supports the same fields as `remember` (content [required], type, title, confidence, tags, source, provenance) with the same allowed values; an item without a source is attributed to the calling client. Max 100 items."

addedOutput schema / $defs / BatchRememberItemResult / description
```
Added value: +"Result for one item in a batch memory write."
```

addedOutput schema / description

Added value: +"Response returned by the batch_remember MCP tool."

First observedv0.1.0Jul 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It adds useful context beyond the schema, such as the 'item without a source is attributed to the calling client' and the emphasis on 'independent facts.' However, it does not mention potential partial failures, idempotency, or other side effects, which would be richer context.

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?

The description is extremely concise, consisting of two front-loaded sentences that convey purpose, usage context, and an alternative. Every word adds value, and it avoids redundancy with the schema.

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 rich schema and presence of an output schema, the description covers purpose, usage, and distinctions effectively. It lacks an explicit note on error handling or atomicity, which might be relevant for a batch operation, but overall it is sufficiently complete for agent decision-making.

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 the schema itself already explains the `memories` parameter, including field details, limits, and source attribution. The tool description does not add new parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 the tool's function with a specific verb and resource: 'Store many memories at once (up to 100).' It also distinguishes itself from the sibling tool `remember` by explicitly saying 'For a single item, prefer `remember`.'

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?

The description provides explicit when-to-use guidance: 'Use this when you have a list of independent facts to persist - e.g. extracting structured data from a document.' It also gives an exclusion by directing single-item use to `remember`, which clarifies the appropriate context for each tool.

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

Deploy Server