Maindex Expert Memory Service

This connector has been deprecated

Replaced by Maindex Expert Memory Service.

Duplicate entry

memory_bulk_keep

Create multiple memories in one call (max 100) with shared defaults. Tags and collections are merged per-item. Mutates. Not idempotent — calling twice creates duplicates. Auto-links batch members with mentioned_with links unless auto_link is false. Returns { created, memories } with id and shortId per item. CONTENT POLICY: NEVER store passwords, API keys, secrets, credit card numbers, SSNs, government IDs, medical/health records (PHI/HIPAA), biometric data, or any legally protected PII. Sanitize content before storing.

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": "memory_bulk_keep"
  }
}

Input Schema

Name	Required	Description
`defaults`	No	Shared defaults applied to all memories in the batch
`memories`	Yes	Array of memories to create (1-100)
`auto_link`	No	Auto-create mentioned_with links between batch members

Output Schema

Name	Required	Description
`created`	Yes	Number of memories created
`memories`	Yes	Created memory objects
`link_summary`	Yes	Summary of links created

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations it discloses non-obvious side effects: automatic mentioned_with links between batch members (unless auto_link is false), the duplicate risk on re-invocation, the shape of the response ({ created, memories }), and an explicit content policy. The 'Mutates' line restates readOnlyHint=false but is backed up with real consequence detail.

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?

Purpose and limits are front-loaded, followed by side effects and return shape, with the content policy last where it belongs. The content policy sentence is long but is a substantive safety constraint rather than filler.

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?

For a high-complexity nested batch-write tool this covers the essentials: batch limit, defaults/merge behavior, auto-linking, duplicate risk, and response shape. An output schema exists, so the brief return-value mention is sufficient, and the remaining omission (partial-failure semantics) is minor.

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%, so the schema already defines the parameters. The description still adds value by explaining the merge semantics ('Tags and collections are merged per-item') and the auto_link toggle, which clarifies how defaults interact with per-item values.

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?

States a specific verb and resource with scope: 'Create multiple memories in one call (max 100) with shared defaults.' The word 'multiple' and the batch cap implicitly distinguish it from the singular memory_keep sibling, so an agent can select it without opening the schema.

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?

Gives clear usage context (batch creation, 1-100 items, shared defaults merged per-item) and a concrete caution about retry behavior ('calling twice creates duplicates'). It does not explicitly name alternatives such as memory_keep or memory_bulk_update, so the when-not-sibling routing is left implicit.

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

All Maindex Expert Memory Service tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?