Maindex Smart Memory Service

This connector has been deprecated

Replaced by Maindex Smart Memory Service.

Duplicate entry

recall

Read-onlyIdempotent

Search and retrieve memories from Maindex (Smart). Modes: relevant (default), exact, current_state, history, recent. query is required unless mode is recent. Read-only for tenant memory data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recall"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Recall mode: relevant (semantic search), exact (literal match), current_state (latest revision only), history (revision trail), recent (newest first).	relevant
`team`	No	Limit recall to a team workspace (team slug). Omit for personal scope.
`limit`	No	Maximum results (default 20).
`query`	No	Search text. Required unless mode is `recent`. Omit for a recency-sorted list (optionally filtered).
`filters`	No	Optional filters applied to recall results.

Output Schema

Name	Required	Description
`items`	Yes	Matching memory items
`total`	Yes	Total number of matching memories
`traceId`	Yes	Trace ID for debugging
`synthesis`	No	LLM-generated synthesis when entropy is high

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. 'Read-only for tenant memory data' largely restates that, adding only a scope hint; nothing is said about result caps, pagination, or scope interaction between team and personal memory.

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?

Three tight sentences, front-loaded with purpose then constraints, with no filler. Minor redundancy from re-listing modes that the schema already enumerates, but it aids quick mode selection.

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?

With an output schema present, return values need not be described, and annotations cover safety. The description supplies purpose, the mode set, and the key requirement rule, leaving only minor gaps (what 'Maindex (Smart)' refers to, team vs personal scoping behavior).

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 enum documents each mode in more detail than the description does. The description's only substantive parameter claim, the query/mode dependency, is already stated verbatim in the query schema description, so no meaning is added beyond the schema.

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 pair (search and retrieve) and resource (memories from Maindex), and the mode enumeration signals this is the read path. It implicitly contrasts with the mutating siblings (keep, update, forget) but never names them 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?

Gives one concrete usage rule ('query is required unless mode is recent'), which is the most common failure mode for this tool. However, it offers no guidance on choosing between the five modes (relevant vs exact vs current_state vs history) beyond restating the enum, and no when-to-use-vs-siblings direction.

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

All Maindex Smart 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?