Skip to main content
Glama
Sign In
N3MemoryCore MCP — Lite (Ephemeral)

N3MemoryCore MCP — Lite (Ephemeral)

by NeuralNexusNote
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

repair_memory

Re-ensure the RediSearch index to maintain memory search integrity. Idempotent operation returns status and message.

Instructions

Re-ensure the RediSearch index (idempotent). Returns {status, message}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided; description only mentions idempotency and return format. Missing disclosure of potential time consumption, side effects on other operations, or error conditions. For a repair tool, more detail is expected.

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?

Single sentence covering core purpose, idempotency, and return value. Efficient but could benefit from a bit more specificity on what 're-ensure' means operationally.

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

Completeness3/5

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

Description covers basic function and return but lacks context on when/why to invoke this tool. Given no output schema and no annotations, it is minimally adequate for a simple repair operation but not comprehensive.

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?

No parameters in input schema, so description naturally adds no parameter details. Per guidelines, baseline is 4 for zero-parameter tools. The description is sufficient.

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 clearly states it re-ensures the RediSearch index and notes idempotency. The verb 're-ensure' is somewhat ambiguous but generally conveys a repair/maintenance action. It distinguishes from siblings which are CRUD operations on memories.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like delete_memory or search_memory. It lacks context such as prerequisites or typical use cases (e.g., after index corruption).

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

Deploy Server

Other Tools