Skip to main content
Glama

health_check

Run diagnostics on the memory system to identify expiring short-term memories, timeline gaps, and conflicting long-term chunks for memory hygiene maintenance.

Instructions

Run comprehensive demo memory system diagnostics. Returns chunk counts by type and visibility, identifies expiring short-term memories that need promotion, detects timeline coverage gaps, and finds conflicting or redundant long-term chunks. Use this regularly to maintain memory hygiene and before batch promotion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_window_hoursNoAlert when short-term memories will expire within this window
gap_daysNoDetect long-memory timeline gaps over this day threshold
topic_limitNoMaximum topics to return for rich/sparse/volatile sections
page_sizeNoPagination size for loading rows from Supabase
max_rowsNoSafety cap for total rows loaded per table
conflict_similarity_thresholdNoSimilarity threshold for conflict candidate detection
conflict_window_daysNoWithin this day window classify similar pairs as CONFLICT (otherwise SUPERSEDED)
conflict_match_countNoMaximum similar pair records to return from conflict detection
conflict_scan_limitNoMaximum recent chunks scanned for conflict detection
conflict_neighbor_limitNoNearest neighbors compared per chunk in conflict detection
forget_candidate_daysNoOnly suggest forget candidates older than this number of days
forget_candidate_limitNoMaximum forget candidates returned by health_check
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses it is non-destructive (diagnostic) and outlines checks performed. Lacks specifics on output format or performance impact, but sufficient for understanding behavior.

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?

Two sentences: first defines what the tool does, second provides usage guidance. No redundant information. Every sentence adds value and 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 12 parameters with full schema descriptions and no output schema, the description adequately explains return values (chunk counts, expiring memories, gaps, conflicts). Could mention pagination or output format, but overall complete for a diagnostic tool.

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 coverage is 100% with detailed parameter descriptions. Description adds no extra meaning beyond the schema; it focuses on tool purpose rather than parameter details. Baseline 3 is appropriate.

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 'Run comprehensive demo memory system diagnostics' and lists specific outputs (chunk counts, expiring memories, timeline gaps, conflicts). Differentiates from sibling tools like batch_promote, demote_memory, etc., which are operational rather than diagnostic.

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?

Explicitly recommends regular use for memory hygiene and before batch promotion. Context implies diagnostic use case. Does not explicitly discuss when not to use or alternative tools, but guidance is clear and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Marsmanleo/MarsNMe'

If you have feedback or need assistance with the MCP directory API, please join our Discord server