Skip to main content
Glama

mem_doctor

Read-onlyIdempotent

Run read-only SQLite, FTS, foreign-key, and mutation-journal diagnostics on the Leteo memory database to surface integrity issues before they impair AI agent recall.

Instructions

Run read-only SQLite, FTS, foreign-key, and mutation-journal diagnostics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkNoOptional upstream diagnostic check code; the local report includes all checks.
projectNoProject context to report; diagnostics remain store-wide.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkNo
checksNo
issuesNo
healthyNo
projectNo
promptsNo
journal_modeNo
observationsNo
project_statsNoPresent only when a project was explicitly requested and matched.
prompt_fts_okNo
schema_versionNoWhat the store is stamped at, and what this build reads. Carried so an agent can say which of the two is behind when a binary refuses a store.
busy_timeout_msNo
integrity_checkNo
prompt_fts_rowsNo
schema_supportedNo
pending_mutationsNo
observation_fts_okNo
observation_fts_rowsNo
foreign_key_violationsNoThe violations, as examples rather than as an inventory.
foreign_key_violations_omittedNoHow many violations there were beyond the ones listed.
Behavior3/5

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

Annotations already declare read-only/non-destructive, so the description's mention of 'read-only' adds no new behavior. It does add specific diagnostic domains, but no deeper behavioral traits like performance impact or required session state are disclosed.

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?

A single, front-loaded sentence with zero waste. It clearly states action and scope without redundancy.

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, annotations, and full parameter schema coverage, the description covers the essential diagnostic scope. It lacks usage context and report expectations, but those are likely handled by the output schema and sibling tool composition.

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?

Both parameters are fully described in the schema (100% coverage), and the tool description adds no additional parameter information. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 uses the specific verb 'Run' and clearly identifies diagnostic scope (SQLite, FTS, foreign-key, mutation-journal). This distinguishes it from the many sibling memory-management tools, making the purpose unmistakable.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It implies diagnostic use but does not state conditions for invocation, prerequisites, or exclusions.

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/asanabrial/leteo'

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