Skip to main content
Glama
verygoodplugins

mcp-automem

by verygoodplugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check Database Health

check_database_health
Read-onlyIdempotent

Verify AutoMem service health and connected database status, diagnose memory operation failures, and review storage statistics before starting a session.

Instructions

Check the health status of the AutoMem service and its connected databases (FalkorDB graph + Qdrant vectors).

When to use:

  • Before a session to verify the memory service is available

  • When memory operations are failing unexpectedly

  • To check storage statistics

Example:

  • check_database_health({})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if status is error
statusYesOverall health status. degraded means the service is reachable but a backend or sync check needs attention.
backendYesBackend type (automem)
statisticsNoDatabase statistics and diagnostics, including memory/vector counts, sync_status, vector_dimensions, and enrichment state when provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.14.1
    • changedOutput schema / properties / statistics / description
      Previous value: -"Database statistics (memory counts, etc.)"New value: +"Database statistics and diagnostics, including memory/vector counts, sync_status, vector_dimensions, and enrichment state when provided."
    • changedOutput schema / properties / status / description
      Previous value: -"Overall health status"New value: +"Overall health status. degraded means the service is reachable but a backend or sync check needs attention."
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "healthy",
-  "error"
-]New value: +[
+  "healthy",
+  "degraded",
+  "error"
+]
  2. First observedv0.14.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false. Description adds value by specifying the components checked (FalkorDB graph + Qdrant vectors) and the service context (AutoMem). No contradictions.

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?

Extremely concise: one-line purpose, bulleted use cases, and example. Every sentence adds value. Front-loaded with key information.

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?

Given zero parameters and the presence of an output schema, the description is complete. It covers purpose, usage guidance, and provides an example. No gaps.

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 (0 params, baseline 4). Schema coverage is 100%, so description does not need to compensate. The description effectively explains the tool's purpose without needing parameter details.

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?

Description clearly states verb+resource: 'check the health status of the AutoMem service and its connected databases'. Differentiates from sibling tools like store_memory and recall_memory which are CRUD operations.

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?

Provides explicit when-to-use scenarios: before a session, when memory operations fail, and to check statistics. Does not mention when not to use or alternatives, but sibling differentiation makes it clear.

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