Maindex Expert Memory Service

This connector has been deprecated

Replaced by Maindex Expert Memory Service.

Duplicate entry

collection_unlock

Idempotent

Unlock locked memory collections using a passphrase. When collections are locked, their contents are invisible. Provide the passphrase (e.g. 'bright-coral-drift') to unlock them for this session. Mutates session unlock state. Idempotent.

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": {
      "passphrase": "<passphrase>"
    },
    "name": "collection_unlock"
  }
}

Input Schema

Name	Required	Description	Default
`passphrase`	Yes	The unlock passphrase (e.g. 'bright-coral-drift')

Output Schema

Name	Required	Description	Default
`unlockedCount`	Yes	Number of collections unlocked
`unlockedCollections`	No	IDs of unlocked collections

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so restating 'Idempotent' earns nothing. The genuinely additive detail is that unlocking applies 'for this session' rather than permanently, plus the consequence of the locked state (contents invisible). Error behavior on a wrong passphrase remains undisclosed.

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?

Four short sentences, front-loaded with the action and the condition, with no filler. Minor redundancy: the example passphrase is repeated from the schema, and 'Mutates session unlock state' restates what the first sentence already implies.

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 single-parameter mutation tool with full annotations and an output schema, the description covers action, precondition, scope (session-only), and safety posture. Nothing an agent needs in order to call it is missing.

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 coverage and a single documented parameter, the baseline of 3 applies. The description's only parameter-adjacent content is the same example passphrase already present in the schema, so it adds no new meaning about format, source, or validation.

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?

The description opens with a specific verb+resource pair ('Unlock locked memory collections') and names the mechanism (passphrase). It does not distinguish itself from collection_manage, which plausibly also manages collection locking, so an agent cannot fully rule out overlap from the description alone.

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?

It gives a clear triggering condition: use this when collections are locked and 'their contents are invisible.' It does not state exclusions or point to collection_manage for the opposite (locking) operation, so the boundary with siblings is only implied.

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?