Skip to main content
Glama
Sign In
ai-memory-mcp

ai-memory-mcp

by zhanpu89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

maintenance

Idempotent

Rebuild the FTS5 full-text index, compress the database, and persist vector storage to maintain memory performance and reduce storage usage.

Instructions

执行数据库维护：重建 FTS5 全文索引、压缩数据库，并持久化向量存储。

Returns: Dict: {"success": bool, "message": str}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true, and the description elaborates on the actions (rebuild index, compress, persist). This adds useful behavioral context beyond annotations, though it omits potential side effects like performance impact during operation.

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 concise with two sentences: the first lists actions, the second specifies the return type. No unnecessary words, and the main purpose is front-loaded.

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 tool's simplicity and zero parameters, the description covers the core functionality and return format. However, it could mention when maintenance should be invoked (e.g., after frequent inserts) for optimal agent usage.

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?

The tool has no parameters, and schema coverage is 100%. The description does not need to explain parameters, so it meets the baseline with no missing information.

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 purpose: executing database maintenance including rebuilding FTS5 full-text index, compressing the database, and persisting vector storage. This is specific and distinguishes it from sibling tools like search_summaries_fts.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies routine maintenance but lacks context such as prerequisite conditions or post-operation effects.

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